dual interpretation of a field length of a signal unit

专利摘要:
dual interpretation of a unit-length signal field. one method includes receiving, in a first wireless device from a second wireless device, a signal unit (sig) that includes a length field and an aggregation field. the length field is interpreted as a number of symbols in response to the determination that the aggregation field has a first value. the length field is interpreted as a number of bytes in response to the determination that the aggregation field has a second value.
公开号:BR112014004997A2
申请号:R112014004997-1
申请日:2012-09-06
公开日:2020-10-27
发明作者:Sameer Vermani；Mohammad Hossein Taghavi Nasrabadi；Simone Merlin；Santosh Paul Abraham
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

[001] [001] The present application claims priority over the following US Patent Applications assigned to the same assignee, whose contents are expressly incorporated in this document as a reference in full: No. 61 / 531,584 filed on September 6, 2011, No. 61 / 562,063 filed on November 21, 2011, No. 61 / 564,177 filed on November 28, 2011, No. 61 / 566,961 filed on December 5, 2011, No. 61 / 580,616 filed on December 27, 2011, No. 61 / 585,479 filed in 11 and January 2012, No. 61 / 585,573 deposited on January 11, 2012, No. 61 / 670,092 deposited on July 10, 2012, and No. 61 / 684,248 deposited on August 17, 2012. REVELATION FIELD
[002] [002] The present disclosure generally refers to wireless communications and, more specifically, to SIGNAL units (GIS) communicated through wireless networks. BACKGROUND
[003] [003] In many telecommunications systems, communications networks are used to exchange messages between several spatially separate devices in interaction. Networks can be classified according to geographic scope, which could be, for example, a large area, a metropolitan area, a local area or a personal area. Such networks would be designated respectively as a wide area network (WAN), metropolitan area network (MAN), local area network (LAN), or personal area network (PAN). Networks also differ according to the switching / routing technique used to interconnect the various network nodes and devices (for example, circuit switching vs. packet switching), the type of media used for transmission (for example, with wireless vs. wireless), and the set of communication protocols used (for example, Internet protocol set, SONET (Synchronous Optical Network), Ethernet, etc.).
[004] [004] Wireless networks are often preferred when network elements are mobile and thus have dynamic connectivity needs, or if the network architecture is formed in an ad hoc, rather than fixed, topology. Wireless networks employ intangible physical media in a non-targeted propagation mode with the use of electromagnetic waves in the radio frequency bands, microwaves, infrared, optics, etc. Wireless networks advantageously facilitate user mobility and deployment of fast field when compared to fixed wired networks.
[005] [005] The devices on a wireless network can transmit / receive information among themselves. The information may include packages that, in some respects, may be referred to as data units. Packages can include overhead information (for example, header information, package properties, etc.) that helps to route the package over the network, identify the data in the package, process the package, etc., as well as data, for example. example user data, multimedia content, etc. as it may be ported in a package payload. SUMMARY
[006] [006] The systems, methods and devices of revelation each have different aspects, in which none of them are solely responsible for their desirable attributes. Without limiting the scope of this disclosure, as expressed by the claims that follow, some resources will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled “Detailed Description”, a person will understand how the features of this disclosure provide advantages that include reducing the overhead of transmitting payloads in data packets.
[007] [007] In a particular embodiment, a method includes receiving, in a first wireless device from a second wireless device, a signal unit (GIS) that includes a length field and an aggregation field. The method also includes interpreting the length field as numerous symbols in response to determining that the aggregation field has a first value and interpreting the length field as numerous bytes in response to determining that the aggregation field has a second value.
[008] [008] In another particular embodiment, a method includes generating, in a second wireless device, a GIS unit to be transmitted to a first wireless device, in which the GIS unit includes a length field and an aggregation field . The method also includes, in response to determining the use of aggregate transmission for the first wireless device, adjusting the aggregation field to a first value and adjusting the length field for numerous symbols. The method also includes, in response to the determination not to use aggregate transmission for the first wireless device, adjusting the aggregation field to a second value and adjusting the length field to numerous bytes.
[009] [009] In another particular modality, a method includes receiving, on a wireless device, a frame through a sub-1 gigahertz (GHz) wireless network. The frame includes a GIS unit that has a length field and an aggregation field. The method also includes, in response to the determination that the frame is associated with a 1 megahertz (MHz) bandwidth mode, interpreting the length field as numerous bytes or numerous symbols based on an aggregation field value. The method further includes, in response to the determination that the frame is not associated with the 1 MHz bandwidth mode, determining whether the frame includes a short-form preamble or a long-form preamble. The method includes, in response to the determination that the table includes the short format preamble, interpreting the length field as numerous bytes or numerous symbols based on the value of the aggregation field. The method also includes, in response to the determination that the frame includes the long format preamble, determining whether the frame is a single user frame (SU) or a multiple user frame (MU). The method also includes, in response to the determination that the frame is the SU frame, interpreting the length field as numerous bytes or numerous symbols based on the value of the aggregation field. The method includes, in response to the determination that the frame is the MU frame, interpreting the length field as numerous symbols.
[0010] [0010] In another particular embodiment, an apparatus includes a receiver configured to receive a GIS unit that has a length field and an aggregation field. The apparatus also includes a processor configured to interpret the length field as numerous symbols in response to the determination that the aggregation field has a first value and to interpret the length field as numerous bytes in response to the determination that the aggregation field has a second value.
[0011] [0011] In another particular modality, a device includes a processor configured to generate a GIS unit that has a length field and an aggregation field. The processor is also configured to, in response to the determination to use aggregate transmission, adjust the aggregation field to a first value and adjust the length field for numerous symbols. The processor is further configured to, in response to the determination not to use the aggregate transmission, adjust the aggregation field to a second value and adjust the length field to numerous bytes. The device also includes a transmitter configured to transmit the GIS unit. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] [0012] Figure 1 illustrates an example of a wireless communication system in which aspects of the present disclosure can be employed.
[0013] [0013] Figure 2 shows a functional block diagram of an exemplary wireless device that can be used within the wireless communication system of Figure 1.
[0014] [0014] Figure 3 shows a functional block diagram of exemplary components that can be used in the wireless device in Figure 2 to transmit wireless communications.
[0015] [0015] Figure 4 shows a functional block diagram of exemplary components that can be used on the wireless device in Figure 2 to receive wireless communications.
[0016] [0016] Figure 5 illustrates an example of a physical layer data unit.
[0017] [0017] Figure 6 shows a flow chart of an aspect of an exemplary method for generating and transmitting a unit of data.
[0018] [0018] Figure 7 shows a flowchart of another aspect of an exemplary method for receiving and processing a data unit that includes a signal unit.
[0019] [0019] Figure 8 shows a flowchart of another aspect of an exemplary method for generating and transmitting a unit of data.
[0020] [0020] Figure 9 shows a flowchart of another aspect of an exemplary method for receiving and processing a data unit that includes a signal unit.
[0021] [0021] Figure 10 is a functional block diagram of another example wireless device that can be used within the wireless communication system of Figure 1.
[0022] [0022] Figure 11 is a functional block diagram of yet another exemplary wireless device that can be employed within the wireless communication system of Figure 1. DETAILED DESCRIPTION
[0023] [0023] Various aspects of the systems, devices and methods are described more fully hereinafter with reference to the accompanying drawings. The teachings of the revelation, however, can be realized in very different ways and should not be understood as limited to any specific function or structure presented by this entire revelation. Instead, these aspects are provided so that this disclosure is meticulous and complete, and will completely convey the scope of the disclosure to those skilled in the art. Based on the teachings in this document, a person skilled in the art should understand that the scope of the disclosure is intended to cover any aspect of the systems, apparatus and methods of the invention disclosed in this document, whether deployed independently of or combined with any other aspect of the revelation. For example, an apparatus can be implanted or a method can be practiced using any number of aspects presented in this document. In addition, the scope of the disclosure is intended to cover such apparatus or method that is practiced with the use of another structure, functionality, or structure and functionality in addition to or in addition to the various aspects of the disclosure presented in this document. It is to be understood that any aspect disclosed in this document may be accomplished by one or more elements of a claim.
[0024] [0024] Although particular aspects are described in this document, many variations and permutations of these aspects are covered by the scope of the disclosure. Although some benefits and advantages of particular aspects are mentioned, the scope of the disclosure is not intended to be limited to particular benefits, uses or objectives. Instead, aspects of the disclosure are intended to be widely applicable to different wireless technologies, system configurations, networks and transmission protocols, some of which are illustrated for purposes of example in the Figures and the description below. The detailed description and drawings are merely illustrative of the disclosure rather than limiting, the scope of the disclosure being defined by the appended and equivalent claims thereof.
[0025] [0025] Wireless network technologies can include various types of wireless local area networks (WLANsS). An MWLAN can be used to interconnect nearby devices together, employing widely used networking protocols. The various aspects described in this document can be applied to any communication standard, such as WiFi Or, more generally, any member of the IEEE 802.11 family of wireless protocols. For example, the various aspects described in this document can be used as part of the IEEE 802.1l1ah protocol, which uses sub-1 GHz bands.
[0026] [0026] In some respects, wireless signals in a sub-gigahertz band can be transmitted according to the 802.1lah protocol using orthogonal frequency division multiplexing (OFDM), direct sequence broadcast spectrum communications ( DSSS), a combination of OFDM and DSSS communications, or other schemes. Deployments of the 802.l1l1ah protocol can be used for sensors, meters and smart grid networks. Advantageously, aspects of certain devices that implement the 802.1lah protocol can consume less power than devices that implement other wireless protocols, and / or can be used to transmit wireless signals over a relatively long range, for example, about one kilometer or more.
[0027] [0027] In some deployments, a WLAN includes several devices that are the components that access the wireless network. For example, there can be two types of devices: access points (“APS”) and clients (also referred to as stations, or “STAS”). In general, an AP serves as a hub or base station for the WLAN, and an STA serves as a user of the WLAN. For example, an STA can be a laptop computer, a personal digital assistant (PDA), a mobile phone, etc. In one example, a STA connects to an AP via a WiFi-compatible wireless link (for example, IEEE protocol
[0028] [0028] An access point (“AP”) can also include, be deployed as, or known as, a NodeB, Radio Network Controller (“RNC”), eNodeB, Base Station Controller (“BSC”), Base Transceiver Station (“BTS”), Base Station (“BS”), Transceiver Function (“TF”), Radio Router, Radio Transceiver, or some other terminology.
[0029] [0029] A station (“STA”) can also include, be deployed as, or known as, an access terminal (“AT”), a subscriber station, a subscriber unit, a mobile station, a remote station, a remote terminal, a user terminal, a user agent, a user device, user equipment, or some other terminology. In some deployments, an access terminal can include a cell phone, a cordless phone, a Login Protocol (“SIP”) phone, a local wireless loop station (“WLL”), a personal digital assistant ( “PDA”), a portable device that has wireless capability, or some other suitable processing device connected to a wireless modem. Consequently, one or more aspects taught in this document can be incorporated into a phone (for example, a cell phone or smart phone), a computer (for example, a laptop), a portable communication device, a headset, a portable computing device (for example, a personal data assistant), an entertainment device (for example, a music or video device, or a satellite radio), a gaming system or device, a gaming system device global positioning, or any other suitable device that is configured to communicate wirelessly.
[0030] [0030] As discussed above, some of the devices described in this document may implement the 802.11ah standard, for example. Such devices, whether used as an STA or AP or other device, can be used for smart meter or on a smart grid network. Such devices can provide sensor applications or be used in home automation. The devices can be, instead or in addition to this, used in a health care context, for example, for personal health care. They can also be used for surveillance, to allow broadband Internet connectivity (for example, for use with access points (hotspots)), or to deploy machine-to-machine communications.
[0031] [0031] Figure 1 illustrates an example of a wireless communication system 100 in which aspects of the present disclosure can be employed. The wireless communication system 100 can operate in compliance with a wireless standard, for example, the 802.1l1ah standard. The wireless communication system 100 may include an AP 104, which communicates with STAs 106.
[0032] [0032] A variety of processes and methods can be used for transmissions on the wireless communication system 100 between AP 104 and STAs 106. For example, signals can be sent and received between AP 104 and STAs 106 according to OFDM / OFDMA techniques. If so, the wireless communication system 100 can be referred to as an OFDM / OFDMA system. Alternatively, signals can be sent and received between the AP 104 and the STAs 106 according to CDMA techniques. If so, wireless communication system 100 can be referred to as a CDMA system.
[0033] [0033] A communication link that facilitates the transmission of the AP 104 to one or more of the STAs 106 can be referred to as a downlink (DL) 108, and a communication link that facilitates the transmission of one or more of the STAs 106 to the AP 104 can be referred to as an uplink (UL) 110. Alternatively, a downlink 108 can be referred to as a direct link or a direct channel, and an uplink 110 can be referred to as a reverse link or a reverse channel.
[0034] [0034] AP 104 can act as a base station and provides wireless communication coverage in a basic service area (BSA) 102. AP 104, together with STAs 106 associated with AP 104 and using AP 104 for communication, it can be referred to as a basic service set (BSS). It should be noted that the wireless communication system 100 may not have a central AP 104, but may instead function as a point-to-point network between STAs 106. Consequently, the functions of AP 104 described in this document may alternatively be performed by one or more of STAs 106.
[0035] [0035] As further described in this document, packets (for example, illustrative package 140) (alternatively referred to herein as data units or frames) transmitted between the AP 104 and STAs 106 may include a signal unit (GIS) (alternatively referred to in this document as a GIS field). For example, the GIS unit can be included in a package's physical layer preamble (PHY). The GIS unit can include control information that can be used to decode the packet or a payload of data from the packet.
[0036] [0036] In a particular embodiment, as further described in this document, one or more fields in a GIS unit can support the use of “exceptional” values to indicate alternative data formats, payload lengths, and types. For example, a particular value of a particular field in the GIS unit may indicate that another field in the GIS unit should be interpreted in an unconventional way, that the GIS unit is part of a package that has a zero-length payload, or that the GIS unit is part of a particular type of package. For example, a particular value of an encoding and modulation scheme (MCS) field may indicate that the GIS unit is part of a confirmation packet (ACK) that has a zero length payload (for example, a ACK which is represented entirely by PHY data).
[0037] [0037] Figure 2 illustrates various components that can be used in a wireless device 202 that can be employed within the wireless communication system
[0038] [0038] Wireless device 202 may include a processor 204 that controls the operation of wireless device 202. Processor 204 may also be referred to as a central processing unit (CPU). Memory 206, which can include both read-only memory (ROM) and random access memory (RAM), provides instructions and data for processor 204. A portion of memory 206 can also include non-volatile random access memory (NVRAM ). processor 204 typically performs arithmetic and logic operations based on program instructions stored within memory 206. Instructions in memory 206 can be executable to implement the methods described in this document.
[0039] [0039] Processor 204 may include or be a component of a processing system deployed with one or more processors. The one or more processors can be deployed with any combination of general purpose microprocessors, microcontrollers, digital signal processors (DSPs), field programmable port arrangements (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, distinct hardware components, finite state machines of dedicated hardware, or any other suitable entities that can perform calculations or other information manipulation.
[0040] [0040] The processing system may also include a machine-readable medium for storing software. Software should be widely understood to mean any kind of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or other type. Instructions may include code (for example, in source code format, binary code format, executable code format, or any other suitable code format). The instructions, when executed by one or more processors, cause the processing system to perform the various functions described in this document.
[0041] [0041] The wireless device 202 may also include a housing 208 which may include a transmitter 210 and a receiver 212 to allow the transmission and reception of data between the wireless device 202 and a remote location. Transmitter 210 and receiver 212 can be combined into a transceiver 214. An antenna 216 can be attached to housing 208 and electrically coupled to transceiver 214. Wireless device 202 can also include (not shown) multiple transmitters, multiple receivers, multiple transceivers and / or multiple antennas. As further described in the present document, transmitter 210 can be means for transmitting a GIS unit and receiver 212 can be means for receiving a GIS unit.
[0042] [0042] Wireless device 202 may also include a signal detector 218 that can be used in an effort to detect and quantify the level of signals received by transceiver 214. Signal detector 218 can detect signal characteristics, such as energy total, energy per subcarrier per symbol, and spectral power density. Wireless device 202 may also include a digital signal processor (DSP) 220 for use in processing signals. The DSP 220 can be configured to generate a data unit for transmission. In some respects, the data unit may include a physical layer data unit (PPDU). In some ways, the PPDU is referred to as a package. As further described in this document, one or more of processor 204, signal detector 218, and DSP 220 may be a means for generating a GIS unit, means for interpreting a field length of a GIS unit, means for determining whether a GIS unit field has a value indicating a zero-length payload, and / or means for decoding the GIS unit based on the determination.
[0043] [0043] The wireless device 202 may further include a user interface 222 in some respects. User interface 222 may include a keyboard, a microphone, a speaker and / or a display. User interface 222 can include any element or component that transmits information to a user of wireless device 202 and / or receives user input.
[0044] [0044] The various components of the wireless device 202 can be coupled together by a 226 bus system. The 226 bus system can include a data bus, for example, as well as a power bus, a control signal bus , and a status signal bus, in addition to the data bus. Those skilled in the art will understand that the components of the wireless device 202 may be coupled together or accept or provide inputs with each other using some other mechanism.
[0045] [0045] Although numerous separate components are illustrated in Figure 2, those skilled in the art will recognize that one or more of the components can be combined or commonly implanted. For example, processor 204 can be used to deploy not only the functionality described above in relation to processor 204, but also to deploy the functionality described above in relation to signal detector 218 and / or DSP 220 In addition, each of the components illustrated in Figure 2 can be deployed using a plurality of separate elements.
[0046] [0046] As discussed above, wireless device 202 may include an AP 104 or an STA 106, and may be used to transmit and / or receive communications. For example, wireless device 202 can communicate a packet 240 that includes a GIS unit. As further described in this document, packet 240 may include a GIS unit that has a length field that can be interpreted in multiple ways based on the value of another field in the GIS unit. For example, the length field can be interpreted as countless bytes or countless symbols based on the value of an aggregation field. Alternatively, or in addition, the presence of a particular value in a particular field of the GIS unit may indicate that packet 240 has a zero length payload (for example, it is a short ACK that is entirely represented by PHY data).
[0047] [0047] Figure 3 illustrates various components that can be used in wireless device 202 to transmit wireless communications. The components illustrated in Figure 3 can be used, for example, to transmit OFDM communications. In some respects, the components illustrated in Figure 3 are used to transmit data units with SIGNAL units (for example, packet 240 in Figure 2) in various communication modes, as will be discussed in more detail below. For ease of reference, the wireless device 202 configured with the components illustrated in Figure 3 is hereinafter referred to as a wireless device 202a.
[0048] [0048] The wireless device 202a may include a modulator 302 configured to modulate bits for transmission. For example, modulator 302 can determine a plurality of bit symbols received from processor 204 or user interface 222, for example, by mapping bits to a plurality of symbols according to a constellation. The bits can correspond to user data or control information. In some ways, bits are received in code words. In one aspect, modulator 302 includes a QAM modulator (quadrature amplitude modulation), for example, a 16-QAM modulator or a 64-QAM modulator. In other respects, modulator 302 includes a binary phase shift switching modulator (BPSK) or a quadrature phase shift switching modulator (QPSK).
[0049] [0049] The wireless device 202a may further include a transformation module 304 configured to convert symbols or bits modulated in another way of modulator 302 into a time domain. In Figure 3, transformation module 304 is illustrated as being implemented by a fast inverse Fourier transform (IFFT) module. In some deployments, there may be multiple transformation modules (not shown) that transform data units of different sizes.
[0050] [0050] In Figure 3, modulator 302 and transformation module 304 are illustrated as being implanted in DSP 220. In some respects, however, one or both modulator 302 and transformation module 304 are implanted in processor 204 or in another element of wireless device 202.
[0051] [0051] As discussed above, the DSP 220 can be configured to generate a data unit for transmission. In some respects, modulator 302 and transformation module 304 can be configured to generate a data unit that includes a plurality of fields that includes control information and a plurality of data symbols. Fields that include control information can include one or more training fields, for example, and one or more signal fields (GIS). Each training field can include a known sequence of bits or symbols. Each of the GIS fields can include information about the data unit, for example, a description of a data rate or data unit length.
[0052] [0052] Returning to the description of Figure 3, the wireless device 202a can also include a digital to analog converter (DAC, designated “D / A” in Figure 3) 306 configured to convert the output of the transformation module into a signal analog. For example, the time domain output of transformation module 304 can be converted to a baseband OFDM signal by the digital to analog converter 306. The digital to analog converter 306 can be deployed to processor 204 or another element of the device wireless 202. In some respects, the digital to analog converter 306 is implanted in transceiver 214 or in a data transmission processor.
[0053] [0053] The analog signal can be transmitted wirelessly by transmitter 210. The analog signal can be further processed before being transmitted by transmitter 210, for example, when it is filtered or when it is converted upwards to a carrier frequency or intermediate . In the aspect illustrated in Figure 3, transmitter 210 includes a transmission amplifier 308. Before being transmitted, the analog signal can be amplified by transmission amplifier 308. In some respects, amplifier 308 includes a low-noise amplifier (LNA) .
[0054] [0054] Transmitter 210 is configured to transmit one or more data packets or units in a wireless signal based on the analog signal. Data units can be generated using processor 204 and / or DSP 220, for example, using modulator 302 and transformation module 304 as discussed above. Data units that can be generated and transmitted as discussed above are described in more detail below in relation to Figures 5 to 11.
[0055] [0055] Figure 4 illustrates various components that can be used in wireless device 202 to receive wireless communications. The components illustrated in Figure 4 can be used, for example, to receive communications from OFDM. In some respects, the components illustrated in Figure 4 are used to receive data units that include one or more SIGNAL units (for example, package 240 in Figure 2), as will be discussed in more detail below. For example, the components illustrated in Figure 4 can be used to receive units of data transmitted by the components discussed above in relation to Figure 3. For ease of reference, the wireless device 202 configured with the components illustrated in Figure 4 is hereinafter document referred to as a 202b wireless device.
[0056] [0056] Receiver 212 is configured to receive one or more packets or data units on a wireless signal. Data units that can be received and decoded or otherwise processed, as discussed below, are described in more detail in relation to Figures 5 to 11.
[0057] [0057] In the aspect illustrated in Figure 4, Receiver 212 includes a receiver amplifier 401. Receiver amplifier 401 can be configured to amplify the wireless signal received by receiver 212. In some aspects, receiver 212 is configured to adjust the gain receiver amplifier 401 using an automatic gain control (AGC) procedure. In some respects, automatic gain control uses information in one or more received training fields, such as a short received training field (FTS), for example, to adjust the gain. Those who have common skill in the art will understand methods for performing AGC.
[0058] [0058] The wireless device 202b may include an analog to digital converter (ADC, designated "A / D" in Figure 4) 402 configured to convert the amplified wireless signal from receiver 212 into a digital representation thereof. In addition to being amplified, the wireless signal can be processed before it is converted by the analog to digital converter 402, for example, when it is filtered or down-converted to a base or intermediate band frequency. The analog to digital converter 402 can be implanted in processor 204 or another element of wireless device 202. In some aspects, the analog to digital converter 402 is implanted in transceiver 214 or in a downstream processor.
[0059] [0059] The wireless device 202b may also include a transformation module 404 configured to convert the representation of the wireless signal into a frequency spectrum. In Figure 4, the transformation module 404 is illustrated as being implemented by a fast Fourier transform (FFT) module. oThe transformation module 404 can be programmable, and can be configured to perform FFT with different configurations. In one aspect, for example, the transformation module 404 can be configured to perform a 32-point FFT or a 64-point FFT. In some ways, the transformation module 404 can identify a symbol for each point it uses.
[0060] [0060] The wireless device 202b may further include an equalizer and channel evaluator 405 configured to form an estimate of the channel over which of the data unit it is received, and to remove certain effects from the channel based on the channel estimate. For example, the channel evaluator can be configured to approximate a function to the channel, and the channel equalizer can be configured to apply an inverse of that function to the data in the frequency spectrum.
[0061] [0061] In some respects, the equalizer and channel evaluator 405 use information in one or more received training fields, such as a long training field (LTF), for example, to perform the channel estimation. The channel estimate can be formed based on one or more LTFs received at the beginning of the data unit. This channel estimate can later be used to equalize data symbols that follow one or more LTFs. After a certain period of time or after a number of data symbols, one or more additional LTFs can be received in the data unit. The channel estimate can be updated or a new estimate formed using additional LTFs. This new or updated channel estimate can be used to equalize data symbols that follow additional LTFs. In some ways, the new or updated channel estimate is used to equalize data symbols preceding the additional LTFs again. Those of ordinary skill in the art will understand methods for forming a channel estimate.
[0062] [0062] The wireless device 202b may also include a demodulator 406 configured to demodulate the equalized data. For example, demodulator 406 can determine a plurality of symbol bits emitted by transformation module 404 and channel equalizer and evaluator 405, for example, by reversing a bit mapping into a symbol in a constellation. The bits can be processed or evaluated by processor 204, or used to otherwise display or output information to user interface 222. In this way, data and / or information can be decoded. In some ways, the bits correspond to code words. In one aspect, demodulator 406 includes a QAM demodulator (quadrature amplitude modulation), for example, a 16-0AM demodulator or a 64-Q0AM demodulator. In other respects, demodulator 406 includes a binary phase switching demodulator (BPSK) or a quadrature phase shifting demodulator (QPSK).
[0063] [0063] In Figure 4, the transformation module 404, the equalizer and channel evaluator 405, and the demodulator 406 are illustrated as being implanted in the DSP 220. In some aspects, however, one or more of the transformation module 404, of the equalizer and channel evaluator 405, and demodulator 406 are implanted in processor 204 or another element of the wireless device
[0064] [0064] As discussed above, the wireless signal received at receiver 212 includes one or more data units. Using the functions or components described above, the data units or data symbols on them can be evaluated by decoding or evaluated or otherwise processed. For example, processor 204 and / or DSP 220 can be used to decode data symbols on data units using the transformation module 404, the equalizer and channel evaluator 405, and demodulator 406.
[0065] [0065] Data units exchanged by AP 104 and STA 106 may include control information or data, as discussed above. In the physical layer (PHY), these data units can be referred to as physical layer protocol data units (PPDUs). In some ways, a PPDU can be referred to as a physical layer package or package. Each PPDU can include a preamble and a payload. The preamble can include training camps and a GIS field. The payload can include a Media Access Control (MAC) header or data for other layers and / or user data, for example. In various “modalities, data units may include Mac Protocol Data Units (MPDU) and / or Aggregated Mac Protocol Data Units (A-MPDU). The payload can be transmitted using one or more data symbols. The systems, methods and devices in this document can use data units with training fields whose peak-to-power ratio has been minimized.
[0066] [0066] Data units can be transmitted, for example, in a 1 MHz mode or a 2 MHz mode. The preamble can be common for a normal 1 MHz mode and for a repetition of 2x 1 MHz. In a 2 MHz mode, the GIS field can span 52 tones of data. In some embodiments, a GIS field can be replicated every 2 MHz for transmissions greater than 2 MHz. In addition, for transmission greater than 2 MHz, there may be 2 SIG-A fields and 1 SIG-B field for transmission mode. MU. In some embodiments, in a 1 MHz mode, there can be 6 SIG A fields. In a 1 MHz mode, the SIG field can span 24 tones of data. In some modalities, the 2 MHz PHY transmission is an OFDM-based waveform consisting of 64 tones (52 data tones, 4 pilot tones, 7 protection tones, and 1 DC tone). The tone spacing for other bandwidth modes can be the same as the tone spacing for a 2 MHz mode. In some embodiments, a 1 MHz mode includes 32 tones (24 data tones, 2 pilot tones, 5 protection tones, and 1 DC tone).
[0067] [0067] Figure 5 illustrates an example of a data unit 500. The data unit 500 can include a PPDU for use with the wireless device 202. In one embodiment, the data unit 500 can be used by legacy devices or devices that implement a reduced clock speed or standard version inherited from it.
[0068] [0068] The data unit 500 includes a preamble 510. Preamble 510 can include a variable number of repeated STF 512 symbols, and one or more LTF 514 symbols. In a deployment 10 repeated STF 512 symbols can be sent in a row by two LTF 512 symbols. STF 512 can be used by receiver 212 to perform automatic gain control to adjust the gain of amplifier receiver 401, as discussed above. In addition, the STF 512 sequence can be used by receiver 212 for packet detection, approximate timing, and other adjustments. The LTF 514 can be used by the equalizer and channel evaluator 405 to form an estimate of the channel on which data unit
[0069] [0069] Following the preamble 510 in the data unit 500 is a signal unit 520. The SIGNAL unit 520 can be represented using OFDM and can include information related to the transmission rate, the length of the data unit 500 and similar. The data unit 500 additionally includes a variable number of data symbols 530, such as OFDM data symbols. In one embodiment, preamble 510 may include SIGNAL unit 520. In one embodiment, one or more of the data symbols 530 may be a payload.
[0070] [0070] When data unit 500 is received on wireless device 202b, the size of data unit 500 which includes LTFs 514 can be computed based on SIGNAL unit 520, and STF 512 can be used by receiver 212 to adjust the gain of the amplifier receiver 401. In addition, an LTF can be used by the equalizer and channel evaluator 405 to form an estimate of the channel on which data unit 500 is received. The channel estimate can be used by DSP 220 to decode the plurality of data symbols 530 that follows preamble 510.
[0071] [0071] The data unit 500 illustrated in Figure 5 is just an example of a data unit that can be used in the system 100 and / or with the wireless device 202. Those who have common skill in the art will understand that a number greater or lesser of STFs 412 or LTFs 514 and / or data symbols 530 can be included in data unit 500. In addition, one or more symbols or fields can be included in data unit 500 which is not illustrated in Figure 5 , and one or more of the illustrated fields or symbols can be omitted.
[0072] [0072] When using OFDM, numerous orthogonal subcarriers of the frequency band can be used.
[0073] [0073] As discussed above in relation to Figures 2 and 3, the wireless device 202a can be configured to operate in various FFT modes. In various embodiments, the wireless device 202a can be configured to use a 64-point FFT size in conjunction with a larger bandwidth channel than the 32-point FFT channel. For example, the 64-point FFT channel can be twice the bandwidth of the 32-point FFT channel. In one embodiment, transformation module 304 can be configured to use a 64-point FFT size in conjunction with a 2 MHz channel, and transformation module 304 can be configured to use a 32-point FFT channel that can be a 1 MHz channel. In one embodiment, transformation module 304 can be configured to selectively use a plurality of different FFT sizes. In another embodiment, a plurality of different IFFTS can each be configured to use a different FFT size, the output of which can be selectively routed to the DAC 306.
[0074] [0074] In some embodiments, data unit 500 may include a partial air identifier (AID) or PAID field. The PAID field includes a partial identifier for one or more receivers or STAs 106. The PAID field can be used by each STA 106 as an early indicator of whether STA 106 should receive and decode the remainder of the data unit 500. For For example, if the PAID field indicates that data unit 500 is not intended for a particular STA 106, that STA 106 may discontinue processing of data unit 500 in order to save power.
[0075] [0075] In some embodiments, the PAID field includes a unique identification of STA 106, such as a full local identifier (for example, an AID) of STA
[0076] [0076] In some embodiments, the PAID field is not explicitly transmitted, but is encoded in another field, such as a cyclic redundancy check (CRC) field. For example, a CRC can be calculated with the PAID field and other fields from the data unit 500 that are transmitted. STA 106 receives the transmitted fields and the CRC field. STA 106 then calculates a CRC based on the received fields and the PAID field which indicates that STA 106 should continue to process data unit 500. If the CRC calculated by STA 106 matches the received CRC, STA 106 continues to process data unit 500.
[0077] [0077] In some embodiments, data unit 500 includes multiple sets of parameters. A first set of parameters can include parameters used to determine how long STA 106 is in a sleep mode if data unit 500 is not intended for STA 106. A second set of parameters can include other parameters of data unit 500, such as those discussed below. The PAID field can be included in the second set. In some modalities, each set of parameters is covered by an independent CRC specific to that set. Each STA 106 determines based on the PAID field whether data unit 500 is to be decoded. If the data unit 500 is not to be decoded, STA 106 postpones for a while based on the information in the first set of parameters. In some modalities, CRCs are in the field of GIS. In some embodiments, the CRC of the second set of parameters is in the service field after the preamble, for example, if data unit 500 is for non-AMPDU.
[0078] [0078] In some modalities, the PAID field is in the service field. In such modalities, the PAID field can be sent with the same MCS as the data in the GIS field. In some embodiments, the PAID field can immediately precede the MAC header.
[0079] [0079] In some embodiments, data unit 500 includes a random seed for use by STA 106 to unscramble data. In some embodiments, at least a portion of the PAID field may also be the seed. In some modalities, STA 106 can recognize multiple PAID fields, for example, consecutive, as new seeds for retransmission.
[0080] [0080] In some embodiments, the data unit 500 does not include a service field. In such modalities, the bandwidth can be indicated, for example, in the GIS field or in the MAC header. Similarly, a CRC can be included, for example, in the GIS field or in the MAC header. Additionally, or alternatively, the random seed can be included, for example, in the GIS field or in the MAC header. In some embodiments, the random seed can also be included in the PAID field.
[0081] [0081] In some modalities, the PAID field is scrambled with the data in the GIS field and the scrambled sequence is covered by a CRC. Alternatively, the PAID field can be attached to the GIS field and the set is covered by a CRC.
[0082] [0082] In some embodiments, the PAID field is not static in relation to multiple transmissions for an STA 106. For example, the PAID field can change each transmission or it can change after each number of transmissions.
[0083] [0083] In some embodiments, the receiving STA 106 communicates to the transmitting device the PAID field value or an indication of the PAID field value to use for the next transmission. For example, the next PAID field value or an indication of the next PAID field value can be included in an ACK sent in response to a transmission received from the transmitting device.
[0084] [0084] For example, in a first data unit, AP 104 uses a standard PAID field value, to which STA 106 responds by decoding the first data unit. STA 106 sends an ACK to confirm receipt of the first data unit. In ACK communication, STA 106 indicates a next PAID field value. Subsequently, in a second data unit, AP 104 uses the next PAID field value, to which STA 106 responds by decoding the second data unit.
[0085] [0085] The default PAID field value can be, for example, a broadcast PAID field value or it can be, for example, a PAID field value associated with the particular 4sSTA 106 to which the first and second units of data are intended. The next PAID field value can be, for example, a next in a series of numbers, or it can be, for example, a hash of at least a portion of the first data unit, such as the data from the first data unit.
[0086] [0086] In some embodiments, if the AP 104 does not receive the ACK, the AP 104 can transmit the second data unit using the standard PAID field value or the last PAID field value for which an ACK was received. Consequently, STA 106 can be configured to decode data units that include any of multiple PAID field values. For example, STA 106 can be configured to decode data units that include any of the standard PAID field value, the PAID field value for the last received and decoded data unit, and the indicated PAID field value. in the last ACK transmitted by STA 106. In such modalities, AP 104 can be configured to select one of the multiple PAID field values for STA 106.
[0087] [0087] In some modalities, the PAID field is designated by AP 104 with, for example, a change of management. For example, the PAID field can be reassigned periodically. In some embodiments, STA 106 can request or designate a new PAID field for an upcoming AP 104 transmission. For example, if an STA 106 decodes multiple data units that are not intended for that STA 106, STA 106 can request or designate a new PAID field value.
[0088] [0088] In some systems, unicast packet filtering is possible through the MAC address. In such systems, the PAID field can be useful in enhancing packet filtering based on packet content.
[0089] [0089] In some embodiments, the PAID field can identify a type of data unit. In some embodiments, the PAID field can additionally identify the content of the data unit. For example, if the data unit includes a traffic indication map (TIM) for a group of STAs, the PAID field can identify the group of STAs for which the data unit is intended. In some embodiments, certain values in the PAID field can be used to indicate that the data unit is a flag and to identify the flag change sequence number. If the STA is already up to date, the STA can ignore the remainder of the data unit after processing the PAID field.
[0090] [0090] In one embodiment, for 64-point FET signals, data unit 500 may include a preamble of 240 us 510. Preamble 510 may include a single 2-symbol STF 512, a single 2-symbol LTF 514, and a 2-symbol SIGNAL unit 520. The SIGNAL unit 520 can include one or more of the fields shown below in Table 1. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted or can be of a different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table l1. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table l1. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 1 in the order shown in Table 1. In some embodiments, at least a portion of the multi-field information shown in Table 1 is included in a single field. For example, the first and second fields in Table 1 can be collapsed into a single field that includes information from both the first and second fields. SIG-A field (64-bit FFT) Res E Coding
[0091] [0091] In the aspect shown in Table 1, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can also include a “Num SS” field that indicates the number of spatial streams used. The “Num SS” field can be 2 bits long. The SIGNAL 520 unit may also include an “SGI” field that indicates the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[0092] [0092] The SIGNAL 520 unit can also include a "length" field that indicates the length of the 530 payload. The "length" field can be 12 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 4095 bytes. The SIGNAL 520 unit can also include an “aggregation” field that indicates whether A-MPDU is being used. The “aggregation” field can be 1 bit long.
[0093] [0093] The SIGNAL 520 unit can also include a "BW" field that indicates the bandwidth (BW) used. The "BW" field can be 2 bits long. In several modalities, the "BW" field of 2 bits can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz, or 16 MHz. The SIGNAL 520 unit can also include a “encoding” field that indicates the type of encoding used. be 1 bit long.
[0094] [0094] The SIGNAL 520 unit can also include an “AID” field that indicates the aerial identification (AID) associated with the data unit 500. The “AID” field can be 12 bits long. The SIGNAL unit 520 may further include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can also include a “smoothing” field that indicates whether smoothing is recommended in the channel estimate. The “smoothing” field can be 1 bit long.
[0095] [0095] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of lenght. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[0096] [0096] The SIGNAL 520 unit can also include one or more reserved bits. As shown in the implementation of Table 1, the SIGNAL 520 unit can include 1 reserved bit. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[0097] [0097] In one embodiment, the SIGNAL 520 unit can include one or more of the fields shown below in Table 2. Although the fields are shown with a particular length, and in a particular order, in several modalities, one or more fields can rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 2. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 2. In some modalities, the SIGNAL 520 unit has the fields shown in Table 2 in the order shown in Table 2. In some embodiments, at least a portion of the multi-field information shown in Table 2 is included in a single field. For example, the first and second fields in Table 2 can be collapsed into a single field that includes information from both the first and second fields. SIG-A field (64-bit FFT) Rs E sTBC encoding AND
[0098] [0098] In the aspect shown in Table 2, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can also include a “Num SS” field
[0099] [0099] The SIGNAL 520 unit can also include a "length" field that indicates the length of the 530 payload. The "length" field can be 12 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 4095 bytes. The SIGNAL 520 unit can also include an “aggregation” field that indicates whether A-MPDU is being used. The “aggregation” field can be 1 bit long.
[00100] [00100] The SIGNAL 520 unit can also include a “BW” field that indicates the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz, or 16 MHz. The SIGNAL 520 unit can also include a “coding” field that indicates the type of encoding used. The “encoding” field can be 1 bit long.
[00101] [00101] The SIGNAL 520 unit can also include an “AID” field that indicates the aerial identification (AID) associated with data unit 500. The “AID” field can be 13 bits long. In some modalities, the “AID” field carries the AID to SU, while for MU, the first bit is reserved, the next 6 bits carry the group identifier (GID), and the last 6 bits carry numerous streams of space and time (N; ts) for 2nd, 3rd and 4th users. In some embodiments, certain exceptional values in the “AID” field can be used to identify the specific content of the packet, for example, whether the packet is for multicast or broadcast. The SIGNAL unit 520 may further include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL unit 520 may further include a “beam formed” field that indicates whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00102] [00102] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits or 8 bits in length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00103] [00103] The SIGNAL 520 unit can also include one or more reserved bits. The SIGNAL unit 520 may include, for example, 0 or 4 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[00104] [00104] In one embodiment, for 32-point FEFT signals, the data unit 500 can include a preamble of 360 us. The preamble can include a single 4-symbol 512 STF, a single 2-symbol 514 LTF, and a 3-symbol SIGNAL 520 unit. The SIGNAL 520 unit can include one or more of the fields shown below in Table 3. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 3. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 3. In some modalities, the SIGNAL 520 unit has the fields shown in Table 3 in the order shown in Table 3. In some embodiments, at least a portion of the multi-field information shown in Table 3 is included in a single field. For example, the first and second fields in Table 3 can be collapsed into a single field that includes information from both the first and second fields.
[00105] [00105] In the aspect shown in Table 3, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can also include a “Num SS” field that indicates the number of spatial streams used. The “Num SS” field can be 2 bits long. The SIGNAL 520 unit may also include an “SGI” field that indicates the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 nudes.
[00106] [00106] The SIGNAL 520 unit can also include a "length" field that indicates the length of the 530 payload. The "length" field can be 11 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 4095 bytes. The SIGNAL 520 unit can also include an “aggregation” field that indicates whether A-MPDU is being used. The “aggregation” field can be 1 bit long.
[00107] [00107] The SIGNAL 520 unit can also include a “coding” field that indicates the type of coding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can also include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long.
[00108] [00108] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of lenght. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00109] [00109] The SIGNAL 520 unit can also include one or more reserved bits. As shown in the implementation of Table 3, the SIGNAL 520 unit can include 5 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can allow the receiver to mitigate the impact of 'high time channel variation'
[00110] [00110] In the deployment shown in Table 3, the SIGNAL 520 unit for a 32-point FFT may omit one or more fields used in the SIGNAL 520 unit for the 64-point FFT shown above in Table 1. For example, the fields “BW”, “AID”, and “smoothing” are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00111] [00111] In various modalities, symbols, fields and / or data units can be repeated in order to increase the effective signal-to-noise ratio (SNR) of a transmission. For example, 32-point FFT transmissions can be repeated twice, three times, four times, eight times, etc. In one mode, the repetition can be performed in conjunction with decreasing the transmission clock speed.
[00112] [00112] In one embodiment, for 32-point FFT signals with a two-time repeat mode, data unit 500 can include a preamble of 440 us. The preamble can include a single 4-symbol STF 512, a single 3-symbol LTF 514, and a 4-symbol SIGN unit 520. The SIGNAL 520 unit can include one or more of the fields shown below in Table 4. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 4. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 4. In some modalities, the SIGNAL 520 unit has the fields shown in Table 4 in the order shown in Table 4. In some embodiments, at least a portion of the multi-field information shown in Table 4 is included in a single field. For example, the first and second fields in Table 4 can be collapsed into a single field that includes information from both the first and second fields. 2x Repeat) ss EA Reserved ——— B |
[00113] [00113] In the aspect shown in Table 4, the SIGNAL 520 unit can include a “length” field that indicates the payload length 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 4095 bytes.
[00114] [00114] The SIGNAL 520 unit can also include a “parity” field that indicates the result of a parity calculated in one or more fields of the SIGNAL unit
[00115] [00115] The SIGNAL 520 unit can also include one or more reserved bits. As shown in the deployment of Table 4, the SIGNAL 520 unit can include 8 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[00116] [00116] In the deployment shown in Table 4, the SIGNAL 520 unit for a 32-point FFT may omit one or more fields used in the SIGNAL 520 unit for the 64-point FEFT shown above in Table 1. For example, the fields “MCS”, “Num SS”, “SGI”, “BW”, “AID”, “aggregation”, “encoding” and “STBC” are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00117] [00117] In one mode, a single SIGNAL 520 unit format can be used for 32-point FFT in both non-repetition and two-step repetition modes. The single SIGN 520 unit can be included in a “combined” preamble. In one embodiment, the combined preamble can be 520 us in length. The preamble can include a single 4-symbol 512 STF, a single 3-symbol 514 LTF, and a 6-symbol SIGNAL 520 unit. The SIGNAL 520 unit can include one or more of the fields shown below in Table 5. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 5. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 5. In some modalities, the SIGNAL 520 unit has the fields shown in Table 5 in the order shown in Table 5. In some embodiments, at least a portion of the multi-field information shown in Table 5 is included in a single field. For example, the first and second fields in Table 5 can be collapsed into a single field that includes information from both the first and second fields. | lfield - from SIG-A (32-bit FFT Combined points)
[00118] [00118] In the aspect shown in Table 5, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can also include a “Num SS” field that indicates the number of spatial streams used. The “Num SS” field can be 2 bits long. The SIGNAL 520 unit may also include an “SGI” field that indicates the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 ns.
[00119] [00119] The SIGNAL 520 unit can also include a "length" field that indicates the length of the 530 payload. The "length" field can be 11 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 4095 bytes. The SIGNAL 520 unit can also include an “aggregation” field that indicates whether A-MPDU is being used. The “aggregation” field can be 1 bit long.
[00120] [00120] The SIGNAL 520 unit can also include a “encoding” field that indicates the type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can also include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can also include a “smoothing” field that indicates whether smoothing is recommended in the channel estimate. The “smoothing” field can be 1 bit long.
[00121] [00121] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of lenght. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00122] [00122] The SIGNAL 520 unit can also include one or more reserved bits. As shown in the implementation of Table 5, the SIGNAL 520 unit can include 4 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[00123] [00123] In the deployment shown in Table 5, the SIGNAL 520 unit for a 32-point FFT can omit one or more fields used in the SIGNAL 520 unit for the 64-point FFT shown above in Table 1. For example, the “BW” and “AID” fields are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00124] [00124] In one mode, a single SIGNAL 520 unit format can be used for 32-point FFT in normal and 2x rep modes. The SIGNAL 520 unit can include one or more of the fields shown below in Table 6. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or they can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 6. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 6. In some modalities, the SIGNAL 520 unit has the fields shown in Table 6 in the order shown in Table 6. In some embodiments, at least a portion of the multi-field information shown in Table 6 is included in a single field. For example, the first and second fields in Table 6 can be collapsed into a single field that includes information from both the first and second fields.
[00125] [00125] In the aspect shown in Table 6, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can also include a “Num SS” field that indicates the number of spatial streams used. The “Num SS” field can be 2 bits long. The SIGNAL 520 unit may also include an “SGI” field that indicates the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 pus and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00126] [00126] The SIGNAL 520 unit can also include a "length" field that indicates the length of the 530 payload. The "length" field can be 11 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packet sizes larger than 2047 bytes. The SIGNAL 520 unit can also include an “aggregation” field that indicates whether A-MPDU is being used. The “aggregation” field can be 1 bit long.
[00127] [00127] The SIGNAL 520 unit can also include a “encoding” field that indicates the The type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can also include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL unit 520 may further include a “beam formed” field that indicates whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00128] [00128] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits or 8 bits in length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00129] [00129] The SIGNAL 520 unit can also include one or more reserved bits. The SIGNAL unit 520 may include, for example, 0 or 4 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[00130] [00130] In the deployment shown in Table 6, the SIGNAL 520 unit for a 32-point FFT may omit one or more fields used in the SIGNAL 520 unit for the 64-point FFT shown above in Table 1. For example, the fields “BW” and “AID” are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00131] [00131] In one embodiment, a single SIGNAL 520 unit format can be used for a 64-point FFT MU SIG-B mode. The SIGNAL 520 unit can be sent to each user with pre-coding applied. The SIGNAL 520 unit can include one or more of the fields shown below in Table 7. Although the fields are shown with a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or they can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 7. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 7. In some modalities, the SIGNAL 520 unit has the fields shown in Table 7 in the order shown in Table 7. In some embodiments, at least a portion of the multi-field information shown in Table 7 is included in a single field. For example, the first and second fields in Table 7 can be collapsed into a single field that includes information from both the first and second fields. 64-point FEFT) Bo er E
[00132] [00132] In the aspect shown in Table 7, the SIGNAL 520 unit can include an “MCS” field that indicates the modulation coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can also include a “coding” field that indicates the type of coding used. The “encoding” field can be 1 bit long.
[00133] [00133] The SIGNAL 520 unit can also include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of lenght. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can also include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00134] [00134] The SIGNAL 520 unit can also include one or more reserved bits. The SIGNAL unit 520 may include, for example, 11 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that may allow the receiver to mitigate the impact of 'high time channel variation' during the transmission of the SIGNAL 520 unit.
[00135] [00135] In the deployment shown in Table 7, the SIGNAL 520 unit for a 32-point FFT may omit one or more fields used in the SIGNAL 520 unit for the 64-point FFT shown above in Table 1. For example, the fields “BW” and “AID” are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00136] [00136] In one mode, for 2 MHz, 64-point FFT signals, the data unit 500 can support multiple users. The preamble can include a 2-symbol SIGNAL 520 unit. The SIGNAL 520 unit can include one or more of the fields shown below in Table 8. Although the fields are shown with a particular length, and in a particular order, in various modalities , one or more fields can be rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 8. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 8. In some modalities, the SIGNAL 520 unit has the fields shown in Table 8 in the order shown in Table 8. In some embodiments, at least a portion of the multi-field information shown in Table 8 is included in a single field. For example, the first and second fields in Table 8 can be collapsed into a single field that includes information from both the first and second fields. = 64 points)
[00137] [00137] In some modalities, a first symbol of the SIGNAL 520 unit includes the fields "BW", "1st Reserved", "STBC", "Num SS", "AID / GIDHNsSts", "2nd Reserved", "SGI" , "Coding", "MCS", and "Beam formed", and a second symbol of the SIGNAL 520 unit includes the fields "Aggregation", "Length", "3rd Reserved", "CRC" and "final part".
[00138] [00138] In the aspect shown in Table 8, the SIGNAL 520 unit can include a “BW” field that indicates the bandwidth (BW) used. The “BW” field can be 2 bits long. In several modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz, or 16 MHz. The SIGNAL 520 unit can also include a “1st Reserved” bit. The SIGNAL unit 520 may further include a “STBC” field that indicates whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long.
[00139] [00139] The SIGNAL 520 unit can also include a “Num SS” field that indicates the number of spatial flows used. The “Num SS” field can be 2 bits long. The SINAL 520 unit can also include an “AID / GID + Nsts” field that indicates the aerial identification (AID)
[00140] [00140] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 nudes. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00141] [00141] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission.
[00142] [00142] The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether an A-MPDU is used. The “aggregation” field can be 1 bit long. The SIGNAL unit 520 can additionally include a "length" field indicating the length of payload 530. The "length" field can be 12 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 4095 bytes. The SIGNAL 520 unit can additionally include 3 bits “Reserved in 3rd place”. In alternative modes, the “length” field is 9 bits long and the SIGNAL 520 unit includes 6 bits “Reserved in 30 places”.
[00143] [00143] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00144] [00144] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 8, the bit “Reserved in 1st place” can be used as a 3rd bit for the field “BW ', the bit“ Reserved in 2nd place ”can be used as a 13th bit for the field “AID / GID + Nsts” and / or one or more of the bits “Reserved in 3rd place” can be used as additional bits for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of high time channel variation 'during the transmission of the SIGNAL 520 unit.
[00145] [00145] In one mode, a single SIGNAL 520 unit format can be used for a 64-point FFT SIG-B MU mode. The SIGNAL 520 unit can include one or more of the fields shown below in Table 9.
[00146] [00146] In the aspect shown in Table 9, the SIGNAL 520 unit can include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long.
[00147] [00147] The SIGNAL 520 unit can additionally include 7 reserved bits. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 8 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00148] [00148] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation ” during transmission of the SIGNAL 520 unit.
[00149] [00149] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 10. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 10. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 10. In some modalities, the SIGNAL 520 unit has the fields shown in Table 10 in the order shown in Table 10. In some embodiments, at least a portion of the multi-field information shown in Table 10 is included in a single field. For example, the first and second fields in Table 10 can be collapsed to form a single field that includes information from the first and second fields. SIG-A field (6 BBits Eizo E) SHE
[00150] [00150] In the aspect shown in Table 10, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00151] [00151] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00152] [00152] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00153] [00153] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00154] [00154] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 11 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 2,047 bytes.
[00155] [00155] The SIGNAL 520 unit can additionally include 4 reserved bits. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00156] [00156] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 10, reserved bits can be used as additional bits for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation ” during transmission of the SIGNAL 520 unit.
[00157] [00157] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit may include one or more of the fields shown below in Table 11. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some modalities the SIGNAL 520 unit has all the fields shown in Table 11. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 11. In some modalities, the SIGNAL 520 unit has the fields shown in the Table 11 in the order shown in Table 11. In some embodiments, at least a portion of the multi-field information shown in Table 11 is included in a single field. For example, the first and second fields in Table 11 can be collapsed to form a single field that includes information from the first and second fields.
[00158] [00158] In the aspect shown in Table 11, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00159] [00159] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 pus and a normal guard interval may be 4 us.
[00160] [00160] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00161] [00161] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00162] [00162] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00163] [00163] The SIGNAL 520 unit may additionally include the reserved bit. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00164] [00164] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 12. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table 12. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table 12. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 12 in the order shown in Table 12. In some embodiments, at least a portion of the multi-field information shown in Table 12 is included in a single field. For example, the first and second fields in Table 12 can be collapsed to form a single field that includes information from the first and second fields. SIG-A field (5Bits ste imo |
[00165] [00165] In the aspect shown in Table 12, the SIGNAL 520 unit can include a “STBC” field indicating whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 ps and a normal guard interval may be 8 ps. In some embodiments, a short guard interval can be 2 feet and a normal guard interval can be 4 us.
[00166] [00166] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can additionally include an “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long.
[00167] [00167] The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long. The SIGNAL unit 520 may additionally include a “length” field indicating the length of payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00168] [00168] The SIGNAL 520 unit can additionally include 3 reserved bits. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00169] [00169] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 12, one or more of the reserved bits can be used as additional bits for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of high time channel variation 'during the transmission of the SIGNAL 520 unit.
[00170] [00170] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 13. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table 13. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table 13. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 13 in the order shown in Table 13. In some embodiments, at least a portion of the multi-field information shown in Table 13 is included in a single field. For example, the first and second fields in Table 13 can be collapsed to form a single field that includes information from the first and second fields. | SIG-A field (6BBits ET
[00171] [00171] In the aspect shown in Table 13, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 ps and a normal guard interval may be 8 ps. In some embodiments, a short guard interval can be 2 feet and a normal guard interval can be 4 us.
[00172] [00172] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00173] [00173] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00174] [00174] The SIGNAL 520 unit can additionally include 1 reserved bit. The SIGN 520 unit can additionally include a “parity” field indicating the result of a parity calculated on one or more fields of the SIGN 520 unit. The “parity” field can be 1 bit long. In one embodiment, another error detection code can be used instead of, or in addition to, the parity bit. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00175] [00175] As discussed below, in several modalities, the reserved bit can be used to carry additional information for different types of packets. For example, the reserved bit - can include additional information related to acknowledgment packets (ACK). In some embodiments, the reserved bit can be used to extend the preceding field. For example, in the example shown in Table 13, the reserved bit can be used as an additional bit for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation' during transmission of the SIGNAL 520 unit.
[00176] [00176] In one mode, a single SIGNAL 520 unit format can be used for a 64-point FFT SIG-B MU mode. The SIGNAL 520 unit can include one or more of the fields shown below in the Table
[00177] [00177] In the aspect shown in Table 14, the SIGNAL 520 unit may include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long.
[00178] [00178] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 to 11 bits long. In one modality, the field
[00179] [00179] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00180] [00180] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation ” during transmission of the SIGNAL 520 unit.
[00181] [00181] In one mode, for 64-point 2 MHz FFT signals, the data unit 500 can support multiple users. The preamble can include a 2-symbol SIGNAL 520 unit. The SIGNAL 520 unit can include one or more of the fields shown below in the Table
[00182] [00182] In some modalities, a first symbol of the SIGNAL 520 unit includes the fields “BW,” “Reserved in 1st Place,” “STBC,” “Num SS,” “AID / GID + Nsts,” “Reserved in 2nd Place, ”“ SGI, ”“ Coding ”and“ MCS ”and a second symbol for the SIGNAL 520 unit includes the fields“ Beam formed, ”“ Aggregation, ”“ Length, ”“ Reserved in 3rd place, ”“ CRC ”and "Final Part".
[00183] [00183] In the aspect shown in Table 15, the SIGNAL 520 unit can include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In several modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include a “Reserved in 1st place” bit. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long.
[00184] [00184] The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long. The SIGNAL 520 unit can additionally include an “AID / GID + Nsts” field indicating the aerial identification (AID) associated with data unit 500. The “AID / GID + Nsts” field can be 12 bits long and can include a PAID field as discussed above. In some modalities, the field “AID / GID + Nsts” carries AID to SU, while for MU, the first 6 bits carry GID and the last 6 bits carry Ns.ts for the 2nd, 3rd and 4th users. In some modalities, certain exceptional values of the “AID / GID + Nsts” field can be used to identify the specific content of the package, for example, if the package is for multiple transmission or broadcast. During SU mode, the “AID” bits in the “AID / GID + Nsts” field can be used for modalities that use cell discharge, so that other devices can save power during transmissions. The SIGNAL 520 unit can additionally include a “Reserved in 2nd place” bit.
[00185] [00185] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 pus. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00186] [00186] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. The first bit of the “encryption” field can indicate the type of encryption for a single user or for user O in case of multiple users. The second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol. In the case of multiple users, the second bit of the “encryption” field can be used to indicate whether the low density parity check (LDPC) encoding has resulted in an extra symbol for any of the users. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used.
[00187] [00187] The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long. The SIGNAL unit 520 may additionally include a “length” field indicating the length of payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include 5 “Reserved in 30 place” bits.
[00188] [00188] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00189] [00189] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 14, the bit “Reserved in 1st place” can be used as a 3rd bit for the field “BW ', the bit“ Reserved in 2nd place ”can be used as a 13th bit for the field “AID / GID + Nsts” and / or one or more of the bits “Reserved in 3rd place” can be used as additional bits for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation' during transmission of the SIGNAL 520 unit.
[00190] [00190] In one mode, a single SIGNAL 520 unit format can be used for a 64-point FFT SIG-B MU mode. The SIGNAL 520 unit can be sent to each user with pre-coding applied. The SIGNAL 520 unit can include one or more of the fields shown below in Table 16. Although the fields are shown having a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or they can be of a different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table 16. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table 16. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 16 in the order shown in Table 16. In some embodiments, at least a portion of the multi-field information shown in Table 16 is included in a single field. For example, the first and second fields in Table 16 can be collapsed to form a single field that includes information from the first and second fields. l SIG-B field (MU deiBBits mode FEIST
[00191] [00191] In the aspect shown in Table 16, the SIGNAL 520 unit may include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used.
[00192] [00192] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 8 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00193] [00193] The SIGNAL 520 unit can additionally include one or more reserved bits. The SIGNAL unit 520 may include, for example, 8 reserved bits. As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits “may include additional information related to acknowledgment packets (ACK). In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation' during transmission of the SIGNAL 520 unit.
[00194] [00194] In the implementation shown in Table 16, the SIGNAL 520 unit for a 32-point FFT can omit one or more fields used in the SIGNAL 520 unit for the 64-point FFT shown above in Table 1. For example, the fields “BW 'and“ AID ”are omitted. In one embodiment, certain fields can be omitted due to the fact that the receiving device can implicitly know the parameters indicated in those fields.
[00195] [00195] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 17. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table 17. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table 17. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 17 in the order shown in Table 17. In some embodiments, at least a portion of the multi-field information shown in Table 17 is included in a single field. For example, the first and second fields in Table 17 can be collapsed to form a single field that includes information from the first and second fields.
[00196] [00196] In the aspect shown in Table 17, the SIGNAL 520 unit can include a “STBC” field indicating whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00197] [00197] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 nudes. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00198] [00198] The SIGNAL 520 unit can additionally include a “coding” field indicating the type of coding used. The “encoding” field can be 2 bits long. The first bit of the “encryption” field can indicate the type of encryption for a single user or for user O without multiple users. The second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol. In the case of multiple users, the second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol for any of the users. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00199] [00199] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00200] [00200] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00201] [00201] The SIGNAL 520 unit can additionally include 5 reserved bits. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00202] [00202] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 17, one or more of the reserved bits can be used as additional bits for the “Length” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation' during transmission of the SIGNAL 520 unit.
[00203] [00203] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 18. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 18. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 18. In some modalities, the SIGNAL 520 unit has the fields shown in Table 18 in the order shown in Table 18. In some embodiments, at least a portion of the multi-field information shown in Table 18 is included in a single field. For example, the first and second fields in Table 18 can be collapsed to form a single field that includes information from the first and second fields. SIG-A Field (8BBits Eno
[00204] [00204] In the aspect shown in Table 18, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00205] [00205] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00206] [00206] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. The first bit of the “encryption” field can indicate the type of encryption for a single user or for user O without multiple users. The second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol. In the case of multiple users, the second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol for any of the users.
[00207] [00207] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00208] [00208] The SIGNAL 520 unit can additionally include an “AID” field indicating the aerial identification (AID) associated with data unit 500. The “AID” field can be 9 to 13 bits long and can include a PAID field as discussed above. The SINAL 520 unit can additionally include 2 to 6 reserved bits in 1st place. The total number of bits for the “AID” field and the bits reserved for 1st place can be 15. The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can have 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00209] [00209] The SIGNAL 520 unit can additionally include 2 reserved bits in 20 places. The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits long. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00210] [00210] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 18, one or more of the bits reserved in place can be used as additional bits for the “AID” field and one or more of the bits reserved in 2nd place can be used as additional bits for the field "Length". In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation' during transmission of the SIGNAL 520 unit.
[00211] [00211] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 19. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 19. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 19. In some modalities, the SIGNAL 520 unit has the fields shown in Table 19 in the order shown in Table 19. In some embodiments, at least a portion of the multi-field information shown in Table 19 is included in a single field. For example, the first and second fields in Table 19 can be collapsed to form a single field that includes information from the first and second fields.
[00212] [00212] In the aspect shown in Table 19, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00213] [00213] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00214] [00214] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. The first bit of the “encryption” field can indicate the type of encryption for a single user or for user O without multiple users. The second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol. In the case of multiple users, the second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol for any of the users. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00215] [00215] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field
[00216] [00216] The SIGNAL 520 unit can additionally include an “AID” field indicating the aerial identification (AID) associated with data unit 500. The “AID” field can be 9 bits long and can include a PAID field as discussed above . The SIGNAL unit 520 may additionally include 2 reserved bits. The SIGNAL unit 520 may additionally include a “length” field indicating the length of payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00217] [00217] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00218] [00218] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits can include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the preceding field. For example, in the example shown in Table 19, one or more of the reserved bits can be used as additional bits for the “AID” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the impact of 'high time channel variation ” during transmission of the SIGNAL 520 unit.
[00219] [00219] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 20. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some embodiments, the SIGNAL 520 unit has all the fields shown in Table 20. In some embodiments, the SIGNAL 520 unit has only the fields shown in Table 20. In some embodiments, the SIGNAL 520 unit has the fields shown in Table 20 in the order shown in Table 20. In some embodiments, at least a portion of the multi-field information shown in Table 20 is included in a single field. For example, the first and second fields in Table 20 can be collapsed to form a single field that includes information from the first and second fields.
[00220] [00220] In the aspect shown in Table 20, the SIGNAL 520 unit can include a “STBC” field indicating whether the space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00221] [00221] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 pus and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00222] [00222] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. The first bit of the “encryption” field can indicate the type of encryption for a single user or for user O without multiple users. The second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol. In the case of multiple users, the second bit of the “encoding” field can be used to indicate whether LDPC encoding has resulted in an extra symbol for any of the users. The SIGNAL 520 unit can additionally include a “beam formed” field indicating whether a beamforming direction matrix is applied to the waveform in a SU transmission. The “formed beam” field can be 1 bit long.
[00223] [00223] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00224] [00224] The SIGNAL 520 unit can additionally include an “AID” field indicating the aerial identification (AID) associated with data unit 500. The “AID” field can be 12 bits long and can include a PAID field as discussed above . The SIGNAL unit 520 may additionally include 0 to 6 bits reserved in place.
[00225] [00225] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 bits long. In one embodiment, the The “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include O to 6 bits reserved in 2nd place.
[00226] [00226] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00227] [00227] In one embodiment, for a 1 MHz SIG-A package, the SIGNAL 520 unit can include one or more of the fields shown below in Table 21. Although the fields are shown having a particular length, and in an order in particular, in various embodiments, one or more fields can be rearranged, added, omitted, or can be of different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 21. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 21. In some modalities, the SIGNAL 520 unit has the fields shown in Table 21 in the order shown in Table 21. In some embodiments, at least a portion of the multi-field information shown in Table 21 is included in a single field. For example, the first and second fields in Table 21 can be collapsed to form a single field that includes information from the first and second fields. | l SIG-A Field (7Bits
[00228] [00228] In the aspect shown in Table 21, the SIGNAL 520 unit can include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a “Num SS” field indicating the number of space currents used. The “Num SS” field can be 2 bits long.
[00229] [00229] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00230] [00230] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 1 bit long. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00231] [00231] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include a Doppler / reserved bit, which can be used as a reserved bit or as a Doppler mitigation bit to signal the receiver that there are sections in the SIGNAL 520 unit that can cause the receiver to mitigate the 'high temporal channel variation' impact during transmission of the SIGNAL 520 unit.
[00232] [00232] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit can omit the “end part” field used to restore the state of a convolution encoder and / or decoder and, for example, use end part bit formation, which is more fully described below.
[00233] [00233] In one embodiment, for a 2 MHz GIS package with a short preamble, the SIGNAL 520 unit can include one or more of the fields shown below in Table 22. Although the fields are shown having a particular length, and in in a particular order, in various modalities, one or more fields may be rearranged, added, omitted, or may have a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 22. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 22. In some modalities, the SIGNAL 520 unit has the fields shown in Table 22 in the order shown in Table 22. In some embodiments, at least a portion of the multi-field information shown in Table 22 is included in a single field. For example, the first and second fields in Table 22 can be collapsed to form a single field that includes information from the first and second fields.
[00234] [00234] As discussed below, exceptional values in one or more of the fields shown in the Table
[00235] [00235] In one embodiment, a value of the totality of zero in the "length" field of the 2 MHz GIS packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field may include, for example, short lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10. GIS field (2 symbolsBits FEET
[00236] [00236] In the aspect shown in Table 22, the SIGNAL 520 unit can include a first “Reserved” field that can be 1 bit long. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a second “Reserved” field that can be 1 bit long.
[00237] [00237] The SIGNAL 520 unit can additionally include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include an “Nsts” field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field that can be 2 bits long.
[00238] [00238] The SIGNAL 520 unit can additionally include a “PAID” field indicating a partial association identifier associated with data unit 500. The “PAID” field can be 9 bits long. The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 ps and a normal guard interval may be 8 ps. In some embodiments, a short guard interval may be 2 nudes and a normal guard interval may be 4 us.
[00239] [00239] The SIGNAL 520 unit can additionally include a “Coding” field indicating the type of encoding used. The “Encoding” field can be 2 bits long. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include a “Smoothing” field indicating whether smoothing is recommended in the channel estimate. The “Smoothing” field can be a bit long. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00240] [00240] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include an “ACK indication” field indicating whether the SIGNAL unit is a confirmation. In one mode, the “ACK indication” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), a block acknowledgment (0x01), or not an acknowledgment (0x10). The value of (O0xll) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL unit can include a third “Reserved” field. The third “Reserved” field can be two bits long.
[00241] [00241] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the
[00242] [00242] In one mode, the first field “Reserved”, the field “STBC”, the second field “Reserved”, the field “BW”, the field “Nsts”, the field “PAID”, the field “SGI” , the “Coding” field, the “MCS” field and the “Smoothing” field can be coded using the first GIS-A symbol. In one mode, the “Aggregation” field, the “Length” field, the “ACK indication”, the third “Reserved” field, the “CRC” field and the “Final part” field can be coded using the second SIG-A symbol.
[00243] [00243] In one embodiment, for a 2 MHz SIG-A package with a long preamble and used for a single user, the SIGNAL 520 unit can include one or more of the fields shown below in Table 23. Although the fields are shown to have a particular length, and in a particular order, in various embodiments, one or more fields may be rearranged, added, omitted, or may have a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 23. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 23. In some modalities, the SIGNAL 520 unit has the fields shown in Table 23 in the order shown in Table 23. In some embodiments, at least a portion of the multi-field information shown in Table 23 is included in a single field. For example, the first and second fields in Table 23 can be collapsed to form a single field that includes information from the first and second fields.
[00244] [00244] As discussed below, exceptional values in one or more of the fields shown in the Table
[00245] [00245] In one embodiment, a value of the totality of zero in the "length" field of the 2 MHz SIG-A packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field can include, for example, small lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10. SIG-A field (2Bits EST
[00246] [00246] In the aspect shown in Table 23, the SIGNAL 520 unit can include a “MU / SU” field, indicating whether the SIGNAL unit is for a single user or multiple users. The “MU / SU” field can be a bit long. The “MU / SU” field can be set to zero for the single user. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field
[00247] [00247] The SIGNAL 520 unit can additionally include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include an “Nsts” field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field that can be 2 bits long. The SIGNAL unit 520 can additionally include a “PAID” field indicating a partial association identifier associated with data unit 500. The “PAID” field can be 9 bits long.
[00248] [00248] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 feet and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00249] [00249] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. In one embodiment, the first bit of the “Encoding” field is the encoding type for the single user, while the second bit is the encoding type for LDPC Nsymn ambiguity. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. The “MCS” field can indicate encoding for a single user. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include a “Beam exchange indication” field indicating whether a quadrature component matrix (matrix Q) exchanges initial STF data (D-STF). The “Beam Change Indication” field can be a bit long. The SIGNAL 520 unit can additionally include an “Aggregation” field indicating whether an A-MPDU is used. The “Aggregation” field can be 1 bit long.
[00250] [00250] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include an “ACK indication” field indicating whether the SIGNAL unit is a confirmation. In one mode, the “ACK indication” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), a block acknowledgment (0x01), or not an acknowledgment (0xX10). The value of (O0xll) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL unit can include a second “Reserved” field. The “Reserved” field can be two bits long.
[00251] [00251] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00252] [00252] In one modality, the “MU / SU” field, the “STBC” field, the first “Reserved” field, the “BW” field, the “Nsts” field, the “PAID” field, the “SGI field ”, The“ Coding ”field, the“ MCS ”field and the“ Beam Change Indication ”field can be coded using the first SIG-A symbol. In one modality, the “Aggregation” field, the “Length” field, the “ACK indication” field, the second “Reserved” field, the “CRC” field and the “Final part” field can be coded using the second SIG-A symbol.
[00253] [00253] In one embodiment, for a 2 MHz SIG-A package with a long preamble and used for multiple users, the SIGNAL 520 unit can include one or more of the fields shown below in Table 24. Although the fields are shown having a particular length, and in a particular order, in various embodiments, one or more fields may be rearranged, added, omitted, or may have a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 24. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 24. In some modalities, the SIGNAL 520 unit has the fields shown in Table 24 in the order shown in Table 24. In some embodiments, at least a portion of the multi-field information shown in Table 24 is included in a single field. For example, the first and second fields in Table 24 can be collapsed to form a single field that includes information from the first and second fields.
[00254] [00254] As discussed below, exceptional values in one or more of the fields shown in Table 24 may indicate that one or more fields in the SIGNAL 520 unit should be interpreted differently. For example, when a field in the SIGNAL unit includes an exceptional state, one or more other fields in the SIGNAL unit 520 may include other information related to the alternative frame type, such as an ACK frame, a flag frame, a SYNC flag, a link adaptation frame, etc. Other information may include synchronization information, flag information, link adaptation information, confirmation information, etc. In general, the zero-length payload can be indicated by one or more fields in the SIGNAL 520 unit that have an exceptional condition.
[00255] [00255] In one embodiment, a value of zero in the "length" field of the 2 MHz SIG-A packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field can include, for example, short lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10.
[00256] [00256] In the aspect shown in Table 24, the SIGNAL 520 unit can include a "MU / SU" field, indicating whether the SIGNAL unit is for a single user or multiple users. The "MU / SU" field can be a bit long. The “MU / SU” field can be set to one for multiple users. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a first “Reserved” field that can be 1 bit long.
[00257] [00257] The SIGNAL 520 unit can additionally include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include an “Nsts” field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field can be eight bits long. Two bits of the “Nsts” field can be provided per user for up to four users. The SIGNAL unit 520 can additionally include a “GID” field indicating a group identifier associated with data unit 500. The “GID” field can be 6 bits long.
[00258] [00258] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00259] [00259] The SIGNAL 520 unit can additionally include a “Coding - I” field indicating the type of coding used. The “Encoding - I” field can be 4 bits long. Each bit can indicate an encoding type for each of the four users. The SIGNAL 520 unit can additionally include a "Coding - II" field, indicating ambiguity of LDPC Nsym. The SIGNAL 520 unit can additionally include a “Beam Change Indication” field indicating whether a Q matrix exchanges the initial D-STF. The “Beam Change Indication” field can be a bit long.
[00260] [00260] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include an “ACK indication” field indicating whether the SIGNAL unit is a confirmation. In one mode, the “ACK indication” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), the block acknowledgment (0x01), or not an acknowledgment (0xX10). The value of (O0xl1) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL unit can include a second “Reserved” field.
[00261] [00261] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00262] [00262] In one modality, the “MU / SU” field, the “STBC” field, the first “Reserved” field, the “BW” field, the “Nsts” field, the “GID” field, the “SGI” field and the “Coding-I” field can be coded using the first SIG-A symbol. In one modality, the “Coding - II” field, the “Beam Exchange Indication” field, the “Length” field, the “ACK Indication” field, the second “Reserved” field, the “CRC” field and the “Final Part” field can be coded using the second SIG-A symbol.
[00263] [00263] In one embodiment, for a 1 MHz GIS packet, the SIGNAL 520 unit can include one or more of the fields shown below in Table 25. Although the fields are shown having a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted, or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 25. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 25. In some modalities, the SIGNAL 520 unit has the fields shown in Table 25 in the order shown in Table 25. In some embodiments, at least a portion of the multi-field information shown in Table 25 is included in a single field. For example, the first and second fields in Table 25 can be collapsed to form a single field that includes information from the first and second fields.
[00264] [00264] As discussed below, exceptional values in one or more of the fields shown in Table 25 may indicate that one or more fields in the SIGNAL 520 unit should be interpreted differently. For example, when a field in the SIGNAL unit includes an exceptional state, one or more other fields in the SIGNAL unit 520 may include other information related to the alternative frame type, such as an ACK frame, a flag frame, a SYNC flag, a link adaptation frame, etc. Other information may include synchronization information, flag information, link adaptation information, confirmation information, etc. In general, the zero-length payload can be indicated by one or more fields in the SIGNAL 520 unit that have an exceptional condition.
[00265] [00265] In one embodiment, a value of the totality of zero in the "length" field of the 1 MHz GIS packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field may include, for example, small lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10. | c GIS field (5 or 6Bits
[00266] [00266] In the aspect shown in Table 25, the SIGNAL 520 unit can include an “Nsts” field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field that can be 2 bits long. The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 us. In some embodiments, a short guard interval can be 2 us and a normal guard interval can be 4 “us.
[00267] [00267] The SIGNAL 520 unit can additionally include a “Coding” field indicating the type of encoding used. The “Encoding” field can be 2 bits long. A bit can indicate an encoding type (LDPC / BCC). The second bit may indicate ambiguity of LDPC Nsym. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a first “Reserved” field that can be 1 bit long.
[00268] [00268] The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include an “Aggregation” field indicating whether an A-MPDU is used. The “Aggregation” field can be 1 bit long.
[00269] [00269] The SIGNAL 520 unit can additionally include a “length” field indicating the length of the payload 530. The “length” field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include an “ACK indication” field indicating whether the SIGNAL unit is a confirmation. In one mode, the “ACK indication” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), the block acknowledgment (0x01), or not an acknowledgment (0xX10). The value of (O0xll) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL unit can include a second “Reserved” field. The “Reserved” field can be three bits long.
[00270] [00270] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can have 4 bits of length. In one embodiment, another error detection code can be used instead of, or in addition to, the CRC. The SIGNAL 520 unit may additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00271] [00271] In a modality, a reserved bit is placed right after the first symbol. This can provide new PHY attributes. This provides a total of four (4) reserved bits.
[00272] [00272] In one embodiment, for a 2 MHz GIS package with a short preamble, the SIGNAL 520 unit can include one or more of the fields shown below in Table 26. Although the fields are shown having a particular length, and in in a particular order, in various modalities, one or more fields may be rearranged, added, omitted, or may have a different length.
[00273] [00273] The order of the fields can affect the ratio between the peak and average power of reception or transmission or generation of the packet. Therefore, in some modalities, the order of the fields can be changed to reduce the ratio between the peak and average power experienced during the reception or transmission or generation of the packet. The ratio between peak and average power for a packet with the fields and the field order shown in Table 26 was measured. The measurements show a peak to average power ratio of 11.59 decibels for the first symbol and 9.86 decibels for the second symbol when the reserved bits are set to one (1). When the reserved bits are set to zero, the experimental results showed a peak to average power ratio of 13.4845 decibels for the first symbol and 10.4742 decibels for the second symbol when the reserved bits are set to zero (0) .
[00274] [00274] In some modalities, the SIGNAL 520 unit has all the fields shown in Table 26. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 26. In some modalities, the SIGNAL 520 unit has the fields shown in Table 26 in the order shown in Table 26. In some embodiments, at least a portion of the multi-field information shown in Table 26 is included in a single field. For example, the first and second fields in Table 26 can be collapsed to form a single field that includes information from the first and second fields.
[00275] [00275] As discussed below, exceptional values in one or more of the fields shown in Table 26 may indicate that one or more fields in the SIGNAL 520 unit should be interpreted differently. For example, when a field in the SIGNAL unit includes an exceptional state, one or more other fields in the SIGNAL unit 520 may include other information related to the alternative frame type, such as an ACK frame, a flag frame, a SYNC flag, a link adaptation frame, etc. Other information may include synchronization information, flag information,
[00276] [00276] In one embodiment, a value of the totality of zero in the "length" field of the 2 MHz GIS packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field can include, for example, short lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10.
[00277] [00277] In the aspect shown in Table 26, the SIGNAL 520 unit can include a first “Reserved” field that can be 1 bit long. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a second “Reserved” field that can be 1 bit long.
[00278] [00278] The SIGNAL 520 unit can additionally include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz.
[00279] [00279] The SIGNAL 520 unit can additionally include an "Nsts" field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field that can be 2 bits long.
[00280] [00280] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some modalities, a short guard interval can be 2 us and a normal guard interval can be 8 1ps. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00281] [00281] The SIGNAL 520 unit can additionally include a “Encoding” field indicating the type of encoding used. The “Encoding” field can be 2 bits long. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QOPSK) switching is used. The SIGNAL 520 unit can additionally include a “Smoothing” field indicating whether smoothing is recommended in the channel estimate. The “Smoothing” field can be a bit long. The SIGNAL 520 unit can additionally include an “aggregation” field indicating whether A-MPDU is used. The “aggregation” field can be 1 bit long.
[00282] [00282] The SIGNAL 520 unit can additionally include a “PAID” field indicating a partial association identifier associated with data unit 500. The “PAID” field can be 9 bits long. The SIGNAL 520 unit can additionally include an “ACK indication” field indicating whether the SIGNAL unit is a confirmation. In one mode, the “ACK indication” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), the block acknowledgment (0x01), or not an acknowledgment (0xX10). The value of (O0xll) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL unit can include the third “Reserved” field. The third “Reserved” field can be two bits long.
[00283] [00283] The SIGNAL 520 unit may additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed on a or SIG-A symbol. In one modality, the “Aggregation” field, the “PAID” field, the “ACK indication” field, the third “Reserved” field, the “CRC” field and the “Final part” field can be coded using the second SIG-A symbol.
[00285] [00285] In a modality, a reserved bit is placed in the first symbol. This can provide new PHY attributes.
[00286] [00286] In one embodiment, generating or receiving a first symbol from a 2 MHz short preamble GIS field with fields ordered as shown in Table 26 can provide a maximum peak to average ratio (PAPR) less than than 7.1 decibels. This PAPR can be measured using open-loop transmission, a 256-byte packet, aggregation off, the ACK Indication field set to ACK, a flow, MCSO and MCS7. All combinations of the remaining unspecified fields can be considered when determining this PAPR. The CRC field uses the least significant four bits (LSB) of the regular 8-bit CRC field in
[00287] [00287] In one embodiment, for a 2 MHz SIG-A package with a long preamble and used for a single user, the SIGNAL 520 unit can include one or more of the fields shown below in Table 27. Although the fields are shown to have a particular length, and in a particular order, in various embodiments, one or more fields may be rearranged, added, omitted, or may have a different length.
[00288] [00288] The order of the fields can affect the ratio between the peak and average power of reception or transmission or generation of the packet. Therefore, in some modalities, the order of the fields can be changed to reduce the ratio between the peak and average power experienced during the reception or transmission or generation of the packet. The ratio between peak and average power for a packet with the fields and the field order shown in Table 27 was measured. The measurements show a peak to average power ratio of 11.1304 decibels for the first symbol and 10.4442 decibels for the second symbol when the reserved bits are set to one (1). When the reserved bits are set to zero, the experimental results showed a peak to average power ratio of 13.4845 decibels for the first symbol and 8.8606 decibels for the second symbol when the reserved bits are set to zero (0) .
[00289] [00289] In some modalities, the SIGNAL 520 unit has all the fields shown in Table 27. In some modalities, the SIGNAL 520 unit has only the fields shown in Table 27. In some modalities, the SIGNAL 520 unit has the fields shown in Table 27 in the order shown in Table 27. In some embodiments, at least a portion of the multi-field information shown in Table 27 is included in a single field. For example, the first and second fields in Table 27 can be collapsed to form a single field that includes information from the first and second fields.
[00290] [00290] As discussed below, exceptional values in one or more of the fields shown in Table 27 may indicate that one or more fields in the SIGNAL 520 unit should be interpreted differently. For example, when a field in the SIGNAL unit includes an exceptional state, one or more other fields in the SIGNAL unit
[00291] [00291] In one embodiment, a value of the totality of zero in the “length” field of the 2 MHz SIG-A packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another embodiment, a value of one in the “MCS” field may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, exceptional values in the “length” field can indicate the number of data symbols after the PHY preamble and, optionally, in which MCS the symbols are encoded. Exceptional values in the “length” field can include, for example, short lengths, such as 0, 1, 2, 3, or values less than, for example, 5 or 10.
[00292] [00292] In the aspect shown in Table 27, the SIGNAL 520 unit can include a “MU / SU” field, indicating whether the SIGNAL unit is for a single user or multiple users. The “MU / SU” field can be a bit long. The “MU / SU” field can be set to zero for the single user. The SIGNAL unit 520 can additionally include a “STBC” field indicating whether space-time block encoding (STBC) is used. The “STBC” field can be 1 bit long. The SIGNAL 520 unit can additionally include a first “Reserved” field that can be 1 bit long.
[00293] [00293] The SIGNAL 520 unit can additionally include a “BW” field indicating the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include an “Nsts” field. The “Nsts” field can provide the number of space and time flows (STS). The “Nsts” field that can be 2 bits long.
[00294] [00294] The SIGNAL 520 unit can additionally include a "length" field indicating the length of the payload 530. The "length" field can be 9 bits long. In one embodiment, the “length” field can indicate the length of the payload 530 in units of symbols when A-MPDU is used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes.
[00295] [00295] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short guard interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 8 nudes. In some embodiments, a short guard interval may be 2 us and a normal guard interval may be 4 us.
[00296] [00296] The SIGNAL 520 unit can additionally include a “encoding” field indicating the type of encoding used. The “encoding” field can be 2 bits long. In one embodiment, the first bit of the “Encoding” field is the encoding type for the single user, while the second bit is the encoding type for LDPC Nsym ambiguity. The SIGNAL 520 unit can additionally include an “MCS” field indicating the modulation and coding scheme (MCS) used. The “MCS” field can be 4 bits long. The “MCS” field can indicate encoding for a single user. In case of multiple users, some bits of the “MCS” field can be used to indicate the encoding for users 1 to 3. For example, the first, second and third bits of the “MCS” field can be used to indicate the coding for users 1, 2 and 3, respectively. In one mode, the “MCS” field may indicate that, for example, quadrature phase shift (QPSK) switching is used. The SIGNAL 520 unit can additionally include a “Beam exchange indication” field indicating whether a Q matrix exchanges the initial D-STF. The “Beam Change Indication” field can be a bit long. The SIGNAL 520 unit can additionally include an “Aggregation” field indicating whether an A-MPDU is used. The “Aggregation” field can be 1 bit long.
[00297] [00297] The SIGNAL 520 unit can additionally include a “PAID” field indicating a partial association identifier associated with data unit 500. The “PAID” field can be 9 bits long.
[00298] [00298] The SIGNAL 520 unit may additionally include an “ACK Indication” field that indicates whether the SIGNAL Unit is a confirmation. In one mode, the “Indication ACK” field can indicate whether the SIGNAL 520 unit is an acknowledgment (0x00), a block acknowledgment (0x01), or not an acknowledgment (0x10). The value of (O0xl11) can be reserved. The “Indication ACK” field can be two bits long. The SIGNAL Unit can include a second “Reserved” field. The “Reserved” field can be two bits long.
[00299] [00299] The SIGNAL 520 unit can additionally include a “CRC” field that indicates the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits of lenght. In one embodiment, another error detection code can be used in place of or in addition to the CRC. The SIGNAL 520 unit can additionally include a “Final Part” field used to restore the state of a convolution encoder and / or decoder. The “Final Part” field can be 6 bits long.
[00300] [00300] In one modality, the field “MU / SU”, field “STBC”, first field “Reserved”, field “BW”, field “Nsts”, field “Length”, field “SGI”, field “Coding” , “MCS” field, and “Beam change indication” field can be coded using the first SIG-A symbol. In one modality, the “Aggregation” field, “PAID” field, “ACK indication” field, second “Reserved” field, “CRC” field and “Final part” field can be coded using the second SIG-A symbol .
[00301] [00301] In one embodiment, the generation or receipt of a first symbol from a 2MHz preamble single user SIG-A field with fields ordered as described in Table 27 can result in a maximum ratio between peak power and the average power that is less than 8.7 decibels. This PAPR can be measured using a single user BF transmission, a 256 byte packet, aggregation off, the ACK Indication field set to ACK, a flow and MCS7. All combinations of the remaining unspecified fields can be considered when determining that PAPR. The CRC field uses the least significant four bits (LSB) of the regular 8-bit CRC field in 802, 1111 or 802, 11ac. QBPSK modulation is used for both GIS symbols. 4x oversampled IFFT is also used. The maximum PAPR value above was determined by measuring the PAPR over all combinations of the unspecified fields.
[00302] [00302] In one embodiment, for a 2 MHz SIG-A package with a long preamble and used for multiple users, the SIGNAL 520 unit can include one or more of the fields shown below in Table 28. Although the fields are shown having a particular length, and in a particular order, in various modalities, one or more fields can be rearranged, added, omitted or can be of a different length. In some modalities, the SIGNAL 520 unit has all the fields shown in Table 28.
[00303] [00303] The ordering of the fields can affect the ratio between the peak power and the average power of receiving or transmitting or generating the packet. Therefore, in some modalities, the ordering of the fields can be changed to reduce the ratio between the peak power and the average power experienced when receiving or transmitting or generating the packet. The ratio between peak power and average power for a package with the fields and field order shown in Table 28 was measured. The measurements show a ratio between peak power and average power of 11.8997 decibels for the first symbol and 11.014 decibels for the second symbol when the reserved bits are set to one (1). When the reserved bits are set to zero, experimental results have shown a ratio between peak power and average power of 10.6865 decibels for the first symbol and 11.8570 decibels for the second symbol when the reserved bits are set to zero (0).
[00304] [00304] In some modalities, the SIGNAL 520 unit has only the fields shown in Table 28. In some modalities, the SIGNAL 520 unit has the fields shown in Table 28 in the order shown in Table 28. In some modalities, at least a portion of the multi-field information shown in Table 28 is included in a single field. For example, the first and second fields in Table 28 may collapse into a single field including information from both the first and second fields.
[00305] [00305] As discussed below, the exceptional values in one or more of the fields shown in Table 28 may indicate that one or more fields of the SIGNAL 520 Unit must be interpreted differently. For example, when a field in the SIGNAL Unit includes an exceptional state, one or more other fields of the SIGNAL 520 unit may include other information related to the alternative frame type, such as an ACK frame, a signal frame, a signal frame SYNC, a link adaptation framework, etc. Other information may include synchronization information, flag information, link adaptation information, confirmation information, etc. In general, a zero-length payload can be indicated by one or more fields in the SIGNAL 520 unit having an exceptional condition.
[00306] [00306] In one embodiment, a value of all zeros in the "length" field of the 2 MHz SIG-A packet may indicate that one or more of the reserved bits may indicate an alternative frame type. In another modality, a value of the total of one in the “MCS” field may indicate that the payload length is zero, and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero, and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, the exceptional values in the “length” field may indicate how the GIS field should be interpreted. In some embodiments, the exceptional values in the “length” field can indicate the number of data symbols following the PHY preamble and, optionally in which MCS the symbols are encoded. Exceptional values in the “length” field may include, for example, short lengths, such as 0, 1, 2, 3 or values less than, for example, 5 or 10. symbols) AND
[00307] [00307] In the aspect shown in Table 28, the SIGNAL 520 unit can include a “MU / SU” field, which indicates whether the SIGNAL Unit is for a single user or multiple users. The MU / SU ”field can be a bit long. The “MU / SU” field can be set to one for multiple users. The SIGNAL Unit 520 may additionally include a “STBC” field that indicates whether the space-time block (STBC) encoding is used. The “STBC” field can be 1 bit long. The SIGNAL Unit 520 can additionally include a first “Reserved” field which can be a bit long.
[00308] [00308] The SIGNAL 520 unit can additionally include an "Nsts" field. The “Nsts” field can provide the number of space-time streams (STS). The "Nsts" field can be eight bits long. Two bits of the “Nsts” field can be provided per user by up to four users. The SIGNAL Unit 520 can additionally include a “BW” field that indicates the bandwidth (BW) used. The “BW” field can be 2 bits long. In various modalities, the 2-bit “BW” field can indicate whether the bandwidth is 2 MHz, 4 MHz, 8 MHz or 16 MHz. The SIGNAL 520 unit can additionally include a “GID” field that indicates an group associated with data unit 500. The “GID” field can be 6 bits long.
[00309] [00309] The SIGNAL 520 unit can additionally include an “SGI” field indicating the short surveillance interval (SGI) used. The “SGI” field can be 1 bit long. In some embodiments, a short surveillance interval may be 2 us and a normal surveillance interval may be 8 1us. In some embodiments, a short surveillance interval may be 2 us and a normal surveillance interval may be 4 us.
[00310] [00310] The SIGNAL 520 unit can additionally include a “Coding - I” field indicating the type of coding used. The “Encoding - 1” field can be 4 bits long. Each bit can indicate an encoding type for each of the four users. The SIGNAL 520 unit can additionally include a “Coding-II” field, indicating ambiguity Nsym LDPC. The SIGNAL Unit 520 can additionally include a “Beam Shift Indication” field indicating whether a Q matrix changes D-STF from start. The “Beam Shift Indication” field can be a bit long.
[00311] [00311] The SIGNAL 520 unit can additionally include a "length" field indicating length of payload 530. The "length" field can be 9 bits long. In one embodiment, the “length” field can indicate the payload length 530 in units of symbols when A-MPDU is being used. The “length” field can indicate the payload length 530 in units of bytes when A-MPDU is not being used. In one embodiment, A-MPDU is used for packaged sizes larger than 511 bytes. The SIGNAL Unit 520 can additionally include an “ACK Indication” field indicating whether the SIGNAL Unit is a confirmation. In one mode, the field “Indication ACK” can indicate whether the SIGNAL Unit 520 is an acknowledgment (0x00), a block acknowledgment (0x01), or not an acknowledgment (0xX10). The value of (O0xll) can be reserved. The “ACK indication” field can be two bits long. The SIGNAL Unit can include a second “Reserved” field. The “Reserved” field can be a bit long.
[00312] [00312] The SIGNAL 520 unit can additionally include a “CRC” field indicating the result of a cyclic redundancy check (CRC) computed in one or more fields of the SIGNAL 520 unit. The “CRC” field can be 4 bits of length. In one embodiment, another error detection code can be used in place of or in addition to the CRC. The SIGNAL Unit 520 can additionally include a “final part” field used to restore the state of a convolution encoder and / or decoder. The “final part” field can be 6 bits long.
[00313] [00313] In one mode, the field “MU / SU”, field “STBC”, first field “Reserved”, field “BW”, field “Nsts”, field “GID”, field “SGI” and the field “Coding -I ”can be coded using the first GIS-A symbol. In one mode, the“ Coding-II ”field,“ Beam Change Indication ”field,“ Length ”field,“ ACK Indication ”field, according to “Reserved” field, “CRC” field and “Final part” field can be coded using the second SIG-A symbol.
[00314] [00314] In one embodiment, generating or receiving a second symbol from a GIS field of multiple preamble users of 8 MHz in length with fields ordered as described in Table 28 can result in a maximum ratio between peak power and average power (PAPR) that is less than 11.1 decibels. This PAPR can be measured using multi-user transmission with three users. The group ID is set to three (3). A 1500 byte packet is used, with the ACK Indication field set to ACK block (BA), one flow per user and MCS7. All combinations of the remaining unspecified fields can be considered when determining this maximum PAPR. The CRC field uses the least significant four bits (LSB) of the regular 8-bit CRC field in 802, 1111 or 802, 11ac. QBPSK modulation is used for both GIS symbols. 4x oversampled IFFT is also used. The maximum PAPR value established is determined by measuring the PAPR over all combinations of the unspecified fields.
[00315] [00315] As each of the seven symbols of the SIGNAL 520 unit is represented by a BPSK constellation that has a state of rotation that is both on the real geometry axis and on the imaginary geometry axis, the rotation state of each of the symbols can communicate an additional bit of information. For example, if the first symbol is on the real geometric axis, it can communicate that STBC is activated. Any of the bits of the SIGNAL Unit 520 can be communicated through the symbol rotation status. In the example shown in Table 28, at least one bit is communicated through the rotation status of one of the symbols. In some embodiments, up to six reserved bits can be communicated via the symbol rotation status. The reserved bits communicated through the symbol rotation status can be 1st reserved bits, 2nd reserved bits or a combination of 1 and 2 reserved bits. In some embodiments, for robustness a single bit can be communicated by the rotation status of multiple symbols.
[00316] [00316] As discussed below, in various modalities, reserved bits can be used to carry additional information for different types of packets. For example, reserved bits may include additional information related to acknowledgment packets (ACK). In some embodiments, reserved bits can be used to extend the previous field. For example, in the example shown in Table 19, one or more of the reserved bits can be used as additional bits for the “AID” field. In some embodiments, one or more of the reserved bits are used as one or more Doppler mitigation bits to signal the receiver that there are sections in the SIGNAL 520 unit that can enable the receiver to mitigate the “high time channel variation” impact during transmission of the SIGNAL 520 Unit.
[00317] [00317] In several modalities, one or more fields in the SIGNAL 520 unit can include one or more "exceptional" states or values. An exceptional state may include, for example, a field value that would not normally occur. For example, if the value of the “MCS” field can normally be either “00,” “01,” or “10,” then the value of the whole of one (for example, “l1”) can be considered an exceptional state. As another example, a value of the totality of zeros in the “length” field can be an exceptional state. According to another example, a non-zero value in any of the “reserved” bits can be an exceptional state.
[00318] [00318] The exceptional field states may indicate that one or more fields of the SIGNAL 520 unit must be interpreted differently. For example, when a field in the SIGNAL Unit includes an exceptional state, one or more of the other fields in the SIGNAL 520 unit may include other information related to alternative frame type, such as an ACK frame, a signal frame, a signal frame SYNC, a link adaptation framework, etc. Other information may include synchronization information, flag information, link adaptation information, confirmation information, etc. In general, a zero-length payload can be indicated by one or more fields in the SIGNAL 520 unit having an exceptional condition.
[00319] [00319] In a modality, a value of the totality of zero in the field “length” can indicate that one or more of the reserved bits can indicate an alternative frame type. In another modality, a value of the total of one in the “MCS” field may indicate that the payload length is zero, and that one or more bits in the “length” field contain data related to an alternative frame type. In another embodiment, a non-zero value in one or more “reserved” bits may indicate that the payload length is zero, and that one or more bits in the “length” field contain data related to an alternative frame type. In some modalities, the exceptional values in the “length” field may indicate how the The GIS field should be interpreted. In some embodiments, the exceptional values in the “length” field can indicate the number of data symbols following the PHY preamble, and optionally in which MCS the symbols are encoded. Exceptional values in the “length” field can include, for example, short lengths, such as 0, 1, 2, 3 or values less than, for example, 5 or 10.
[00320] [00320] In some modalities, an exceptional value in the “reserved” bits indicates whether an ACK packet follows the current frame. In some deployments, the “reserved” bits can indicate that the current frame is a control frame, and that the remaining bits are reserved for MAC indications, including length.
[00321] [00321] Table 29 illustrates an example of a GIS field that can be used in a short format preamble in bandwidth modes of 2 MHz or more. The first ten fields of the GIS field (ie Reserved, STBC, Reserved, BW, Nsts, Length, SGI, Encoding, MCS and Smoothing) can be in a first symbol of the GIS field and the last six fields of the GIS field (this ie, Bit aggregation, PAID, ACK indication, Reserved, CRC, and Final part) can be in a second symbol of the SIG field. In a particular mode, at least one reserved bit can be included in the first symbol in the GIS field to provide for a subsequently developed PHY resource.
[00322] [00322] Table 30 illustrates an example of a SIG-A field that can be used in a long format preamble in bandwidth modes of 2 MHz or greater for single user (SU) transmissions. The first ten fields of the SIG-A field (ie, MU / SU, STBC, Reserved bit, BW, Nsts, Length, SsGI, Coding, MCS, and beam shift indication bit) can be in a first symbol of the SIG-A field and the last six fields of the SIG-A field (ie, Aggregation bit, PAID, ACK Indication, Reserved, CRC, and Final Part) can be in a second symbol of the SIG-A field. l Field of SIG-A BitsDescription (long format, 2MHz +, MU) Bit of MU / SU the esster for 1 for MU STBC 2 Aalamouti as STBC in all or no stream A 5 Nsts 2 bits per use for each of the 4 users
[00323] [00323] Table 31 illustrates an example of a SIG-A field that can be used in a long format preamble in 2 MHz or higher bandwidth modes for multi-user transmissions (MU) (for example, for up to four users). The first eight fields in the SIG-A field (that is, bit MU / SU, STBC, Reserved, Nsts, BW, GID, SGI, and I-Coding) can be in a first symbol in the SIG-A field and the last seven fields in the SIG-A field (ie, Coding-II, Reserved, Length, ACK Indication, Reserved, CRC and Final Part) can be in a second symbol in the SIG-A field. It will be noted that the order of the Nsts and BW fields can be reversed when compared to the SU SIG-A field shown in Table 30. This reversal can lead to the improved ratio between peak power and average power (PAPR) for the SIG field. -A of MU shown in Table 31. | SIGBits fieldDescription (1MHz) pts BP | number of streams space time but [Short Surveillance Prtervato Encoding 2 1 bit for encoding type (LDPC / BCC), 2 bit for ambiguity Nsym LDPC
[00324] [00324] Table 32 illustrates an example of a GIS field that can be used in 1 MHz transmissions. In a particular embodiment, the GIS field in Table 32 occupies six symbols (36 bits with 6 bits / symbol in bandwidth of 1 MHz).
[00325] [00325] Figure 6 shows a flow chart of an aspect of an exemplary method 600 of generation and transmission of a data unit. Method 600 can be used to generate any of the data units and SIGNAL Units described above. Data units can be generated on either an AP or a STA and transmitted to another device on the wireless network. Although method 600 is described below in relation to the wireless device elements 202a (Figure 3), those skilled in the art will find that other components can be used to implement one or more of the steps described in this document. Although the steps can be described as occurring in a certain order, the steps can be reordered, the steps can be omitted and / or additional steps can be added.
[00326] [00326] At 602, processor 204 generates a SIGNAL 520 unit. The SIGNAL 520 unit includes at least one encoded PAID field. The PAID field has a value indicating that a portion of the SIGNAL unit must be decoded by one or more devices that receive the SIGNAL unit, and the value of the PAID field indicates that the portion of the SIGNAL unit must not be decoded by one or more than other devices that receive the SIGNAL unit. In one embodiment, modulator 302 can modulate a transmission that includes SIGNAL Unit 520, and transformation module 304 can translate tones that correspond to the transmission in the time domain. Advancing to 604, transmitter 210 transmits a data unit that includes the SIGNAL Unit over a wireless channel.
[00327] [00327] Figure 7 shows a flowchart of another aspect of an exemplary method 700 of receiving and processing a data unit that includes a SIGNAL Unit 520. Method 700 can be used to receive any of the data units described above . Packets can be received either on an AP or a STA from another device on the wireless network. Although method 700 is described below with respect to the elements of wireless device 202b (Figure 4), those skilled in the art will find that other components can be used to implement one or more of the steps described in this document. Although the steps can be described as occurring in a certain order, the steps can be reordered, steps can be omitted and / or additional steps can be added.
[00328] [00328] In 702, receiver 212 receives a SIGNAL 520 unit. The SIGNAL 520 unit includes at least one encoded PAID field. For example, SIGNAL Unit 520 may include one or more of the fields shown above in Tables 1 to 28. Advancing to 704, processor 204 decodes the PAID field. Continuing to 706, processor 204 determines whether the PAID field has a value indicating that an un-decoded portion of the SIGNAL Unit 520 is to be decoded. At 708, processor 204 decodes SIGNAL Unit 520 if the value of the PAID field has a value indicating that SIGNAL Unit 520 is to be decoded. At 710, processor 204 delays for a while if the value of the PAID field does not have a value indicating that SIGNAL Unit 520 must be decoded.
[00329] [00329] In at least some of the modalities discussed above, SIGN 520 Units are encoded using a convolutional code, and end part bits are included in SIGN 520 Units. The end part bits can be a total of zeros , as in a “zero end part code” and are used to return the encoder to the zero state, so that the decoding process at the receiver can be started from the zero state. By adding the final part bits at the end of each SIGNAL 520 Unit, the encoder is returned to the zero state before each SIGNAL 520 Unit. In this way, each SIGNAL 520 Unit can be encoded separately from each other of the SIGNAL 520 Unit by resetting the encoder before each SIGNAL 520 Unit. As independently coded, SIGNAL 520 Units can also be modulated independently. In addition, both the encoder start and end states are known to a decoder used to decode the SIGNAL 520 Unit. As such, each SIGNAL 520 Unit can be decoded and, in some cases, separately demodulated a SIGNAL 520 Unit from another.
[00330] [00330] In some modalities, the SIGNAL Unit 520 can be transmitted as a short block code. For example, any of the modalities discussed in this document can be transmitted as a short block code. Thus, in some modalities, the SIGNAL 520 unit has the end part bits (called “end part bit formation”). For example, the SIGNAL 520 unit can be the same as any of the other modalities discussed in this document except that it has no end bits. For example, any of the modalities discussed with reference to Tables 1 to 28 can be transmitted as a short block code without the final part bits.
[00331] [00331] The SIGNAL 520 unit can be encoded as a linear block code or a short block code using, for example, an extended Hamming code, such as an extended Hamming code of *% rate ( 8, 4, 4). The SIGNAL Unit 520 can be encoded as a short block code using, for example, an extended Golay code, such as a rate = 24 (12, 8) extended Golay code. The SIGNAL Unit 520 can be encoded as a short block code using, for example, a quadratic residue code (OR), such as a% rate QR code (48, 24, 12). The SIGNAL Unit 520 can be encoded as a short block code using, for example, a final part bit forming convolution code (TBCC), such as a TBCC code discussed below.
[00332] [00332] When end part bit formation is used, no end part bits are included in SIGNAL 520 Unit. Instead, the last, for example, "n" bits
[00333] [00333] Figure 8 shows a flow chart of an aspect of an exemplary 800 method of generating and transmitting a data unit. Method 800 can be used to generate any of the data units and SIGNAL Units 520 described above. The data units can be generated in either AP 104 or STA 106 and transmitted to another node on the wireless network. Although method 800 is described below in relation to the wireless device elements 202a (Figure 3), those skilled in the art will find that other components can be used to implement one or more of the steps described in this document. Although the steps can be described as occurring in a certain order, the steps can be reordered, the steps can be omitted and / or additional steps can be added.
[00334] [00334] In 802, processor 204 generates a SIGNAL 520 unit. The SIGNAL 520 unit includes at least one length field and one or more additional fields. For example, the SIGNAL 520 unit may include one or more of the fields shown above in Tables 1 to 28. A first field of one or more additional fields may include an exceptional value indicative of a zero-length payload. As discussed above, an exceptional value may include a field value outside normal operating limits. In one embodiment, modulator 302 can modulate a transmission that includes SIGNAL Unit 520, and transformation module 304 can translate tones that correspond to SIGNAL Unit 520 in the time domain. At 804, transmitter 210 transmits a data unit including SIGNAL Unit 520 over a wireless channel.
[00335] [00335] Figure 9 shows a flowchart of another aspect of an exemplary method 900 of receiving and processing a data unit including a SIGNAL Unit 520. Method 900 can be used to receive any of the data units described above. Packets can be received at either AP 104 or STA 106 from another node on the wireless network. Although method 900 is described below in relation to the elements of wireless device 202b (Figure 4), those skilled in the art will find that other components can be used to implement one or more of the steps described in this document. Although the steps can be described as occurring in a certain order, the steps can be reordered, the steps can be omitted and / or additional steps can be added.
[00336] [00336] In 902, receiver 212 receives a SIGNAL 520 unit. The SIGNAL 520 unit includes at least one length field and one or more additional fields. For example, SIGNAL 520 may include one or more of the fields shown above in Tables 1 to 28. Continuing in 904, processor 204 determines whether a first field in one or more additional fields has an exceptional value indicating a payload zero length. As discussed above, an exceptional value may include a field value outside normal operating limits.
[00337] [00337] Advancing to 906, processor 204 decodes the length field based on the determined exceptional value. For example, the MCS field can include the exceptional value of the whole of one. The processor 204 can then decode the reserved bits and determine an alternative frame type. For example, processor 204 can determine an ACK frame type. The processor 204 can then decode the bits in the length field with respect to one or more parameters of the ACK frame.
[00338] [00338] In a particular mode, a device can generate a GIS unit (for example, the SIGNAL Unit 520) that includes a length field and an aggregation field. For example, the length field can be nine bits long and the aggregation field can be one bit long. Before, after or during the generation of the GIS unit, the device can determine whether or not to use aggregate transmission (for example, A-MPDUs). In a particular embodiment, aggregate transmission may be mandatory for frame sizes greater than or equal to 512 bytes in size, but may be optional for frame sizes less than 512 bytes. In response to the determination to use aggregate transmission, the device can set the aggregation field to a first value (for example, "l") and can set the length field to a number of symbols. In response to the determination not to use aggregate transmission, the device can adjust the aggregation field to a second value (for example, “0”) and can adjust the length field to a number of bytes. The device can transmit the GIS unit over a wireless network (a sub-1 GHz network according to an IEEE 802.1l1ah protocol). The GIS unit can be included in a preamble to a frame, such as a single user (SU) or multiple user (MU) frame.
[00339] [00339] In a particular embodiment, a device can receive a GIS unit (for example, the SIGNAL Unit 520) that includes a length field and an aggregation field. The device can interpret the length field as a number of symbols in response to determining that the aggregation field has a first value (for example, "1"). The device can interpret the length field as a number of bytes in response to the determination that the aggregation field has a second value (for example, “1”).
[00340] [00340] In another particular embodiment, the device can initially determine whether the frame including the GIS unit is associated with 1 MHz bandwidth. If the frame is associated with a 1 MHz bandwidth, the device can interpret the length field as a number of bytes or a number of symbols based on the value of the aggregation field, as described above. However, if the frame is not associated with the MHz bandwidth, the device can determine whether the frame has a short-form preamble or a long-form preamble (for example, by checking a GIS unit rotation). If the frame has a short format preamble, the device can interpret the length field as a number of bytes or a number of symbols based on the value of the aggregation field, as described above. Conversely, if the frame has a long format preamble, the device can determine whether the frame is a SU frame or a MU frame (for example, by checking a SU / MU field). If the frame is a SU frame, the device can interpret the length field as a number of bytes or a number of symbols based on the value of the aggregation field, as described above. If the frame is a MU frame, the device can automatically interpret the length field as a number of symbols (for example, because a wireless or standard protocol, such as IEEE 802.l1lah, can determine that the length of a MU frame having a long format preamble is represented as a number of symbols).
[00341] [00341] Figure 10 is a functional block diagram of another exemplary wireless device 1000 that can be employed in accordance with the present disclosure. Device 1000 includes a generation module 1002 to generate a data unit for wireless transmission. The generation module 1002 can be configured to perform one or more of the functions discussed above in relation to block 602 of Figure 6 and / or block 802 of Figure 8. The generation module 1002 can correspond to one or more of processor 204 and the DSP 220. Device 1000 additionally includes a transmission module 1004 for wirelessly transmitting the data unit. Transmission module 1004 can be configured to perform one or more of the functions discussed above in relation to block 604 in Figure 6 and / or block 804 in Figure 8. Transmission module 1004 can correspond to transmitter 210. In a particular embodiment, the data unit may include a SIGNAL Unit (for example, SIGNAL Unit 520), in which a field of length of the SIGNAL Unit is interpreted based on a value of an aggregation field and / or in which a field particular of the SIGNAL Unit has a value indicating a zero-length payload.
[00342] [00342] Figure 11 is a functional block diagram of yet another exemplary wireless device 1100 that can be employed in accordance with the present disclosure. Device 1100 includes a receiving module 1102 for wirelessly receiving a data unit. Receiving module 1102 can be configured to perform one or more of the functions discussed above in relation to block 702 of Figure 7 and / or block 902 of Figure
[00343] [00343] As used in this document, the term "determine" covers a wide variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (for example, searching a table, a database or other data structure), verifying and the like. In addition, "determination" may include receiving (for example, receiving information), accessing (for example, accessing data in a memory) and the like. In addition, "determining" may include resolving, selecting, choosing, establishing and the like. In addition, a "channel width", as used in this document, may cover or may also be called a bandwidth in certain respects.
[00344] [00344] As used in this document, an expression that refers to "at least one of" a list of items refers to any combination of those items, including only members. As an example, “at least one of: a, b, or c” is intended to cover: only a; only b; only c; a and b; aec; bec; ea, bec.
[00345] [00345] The various operations of the methods described above can be performed by any suitable means that has the ability to perform the operations, such as various component (s), circuits, and / or software and / or hardware module (s). In general, any operation illustrated in the Figures can be performed corresponding to functional means that are capable of carrying out the operations.
[00346] [00346] The various illustrative logic blocks, modules and circuits described in connection with the present disclosure can be implemented or carried out with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable port arrangement signal (FPGA) or other programmable logic device (PLD), discrete port or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described in this document. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any commercially available processor, controller, microcontroller, or state machine. A processor can also be deployed as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core or any other such configuration.
[00347] [00347] In one or more aspects, the functions described can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the functions can be stored or transmitted as one or more instructions or code in a computer-readable medium. The computer-readable medium includes both a computer storage medium and a communication medium including any medium that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to port or store desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, any connection is properly called a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the media definition. Magnetic disk and optical disk, as used in this document, includes compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk and blu-ray disk on which magnetic disks normally reproduce data in a magnetic way , while optical discs reproduce data optically with lasers. Thus, in some respects, the computer-readable medium may include non-transitory computer-readable medium (for example, tangible medium). Furthermore, in some respects, the computer-readable medium may include a transient computer-readable medium (for example, a signal). The above combinations must also be included within the scope of the computer-readable medium.
[00348] [00348] the methods disclosed in this document include one or more steps or actions to achieve the described method. The steps and / or actions of the method can be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.
[00349] [00349] The functions described can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the functions can be stored with one or more instructions in a computer-readable medium. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to port or store desired program code in the form of instructions or data structures and which can be accessed by a computer. The magnetic disk and the optical disk, as used in this document, include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk on which magnetic disks normally reproduce data from magnetic mode, while optical discs reproduce data optically with lasers.
[00350] [00350] Thus, certain aspects may include a computer program product to carry out the operations presented in this document. For example, such a computer program product may include a computer-readable medium that has instructions stored (and / or encoded) in it, the instructions being executable by one or more processors to perform the operations described in this document. For certain aspects, the computer program product may include packaging material.
[00351] [00351] Software or instructions can also be transmitted over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable,
[00352] [00352] Additionally, it must be verified that the modules and / or other appropriate means to carry out the methods and techniques described in this document can be downloaded and / or obtained, otherwise by a user terminal and / or station basis as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means to carry out the methods described in this document. Alternatively, several methods described in this document can be provided through storage media (for example, RAM, ROM, physical storage media such as a compact disc (CD) or floppy disk, etc.), so that a user and / or base station can obtain the various methods by coupling or supplying the storage medium to the device. In addition, any other suitable technique for providing the methods and techniques described in this document to a device can be used.
[00353] [00353] It should be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations can be made to the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.
[00354] [00354] Although what has been said previously is directed to aspects of the present disclosure, other aspects and additional aspects of the disclosure can be delineated without departing from the basic scope of the same, and the scope of the same is determined by the following claims.

权利要求:
Claims (9)
[1]
1. Method, comprising: receiving, in a first wireless device (106) from a second wireless device (104), a signal unit (GIS) (250) via a sub-1 gigahertz wireless network ( GHz); and interpreting a 9-bit length field from the GIS unit, where the 9-bit length field is interpreted as a number of symbols in response to the determination that a 1-bit aggregation field from the GIS unit has a first value , where the 9-bit length field is interpreted as a number of bytes in response to the determination that the 1-bit aggregation field of the SIG unit has a second value, and where the SIG unit corresponds to a format preamble short and with a bandwidth greater than or equal to 2 megahertz (MHz), and in which the SIG unit comprises: a first reserved 1 bit field; a 1-bit space-time block (STBC) code field; a second reserved 1-bit field; a 2-bit bandwidth field; a field of numerous 2-bit space-time streams; a 9-bit partial association identifier field; a 1 bit short guard interval (SGI) field; a 2-bit coding field; a 4-bit coding and modulation scheme field; a 1-bit smoothing field; a 1-bit aggregation field;
a 9-bit length field; a 2-bit acknowledgment indication (ACK) field; a 4-bit cyclic redundancy check (CRC) field; and a final 6-bit field.
[2]
2. Method according to claim 1, wherein the sub-1 GHz wireless network operates according to an 802.11ah protocol from the Institute of Electrical and Electronics Engineers (IEEE).
[3]
3. Method according to claim 1, in which the aggregation field indicates whether the second wireless device is transmitting aggregated media access control protocol (MAC) data units (A-MPDUs) to the first wireless device. thread.
[4]
A method according to claim 1, wherein the GIS unit is included in a preamble to a package.
[5]
5. Apparatus, comprising: mechanisms (1102) for receiving a signal unit (GIS) (250) via a sub-1 gigahertz (GHz) wireless network; and mechanisms (1104) for interpreting a 9-bit length field of the GIS unit, wherein the mechanisms for interpreting interpret the 9-bit length field as a number of symbols in response to the determination that a l1- aggregation field bit of the SIG unit has a first value, and in which the mechanisms for interpreting interpret the 9-bit length field as a number of bytes in response to the determination that the 1-bit aggregation field of the SIG unit has a second value, and in which the SIG unit corresponds to a preamble of short format and a bandwidth greater than or equal to 2 megahertz (MHz), and in which the SIG unit comprises:
a first reserved 1-bit field; a 1-bit space-time block (STBC) code field; a second reserved 1-bit field; a 2-bit bandwidth field; a field of numerous 2-bit space-time streams; a 9-bit partial association identifier field; a 1 bit short guard interval (SGI) field; a 2-bit coding field; a 4-bit coding and modulation scheme field; a 1-bit smoothing field; a 1-bit aggregation field; a 9-bit length field; a 2-bit acknowledgment indication (ACK) field; a 4-bit cyclic redundancy check (CRC) field; and a final 6-bit field.
[6]
6. Apparatus according to claim 5, in which the sub-1 GHz wireless network operates according to an 802.1lah protocol from the Institute of the Institute of Electrical and Electronics Engineers (IEEE).
[7]
Apparatus according to claim 5, in which the aggregation field indicates whether the second wireless device is transmitting media access control protocol (MAC) data units (A-MPDUs) aggregated to the first device without thread.
[8]
Apparatus according to claim 5, wherein the GIS unit is included in a preamble to a package.
[9]
9. Computer program comprising executable instructions for causing at least one computer to execute the method as defined in any one of claims 1 to 4 when executed.

类似技术:

---

公开号 | 公开日 | 专利标题

---

JP6312738B2|2018-04-18|Double interpretation of the length field of the signal unit

---

JP5960267B2|2016-08-02|A signal unit containing a field indicating a zero-length payload

---

ES2761605T3|2020-05-20|Protocol for the response of channel status information

---

US9154363B2|2015-10-06|Systems and methods for wireless communication of packets having a plurality of formats

---

US20130121244A1|2013-05-16|Systems and methods for wireless communication of packets having a plurality of formats

---

US20130279379A1|2013-10-24|Systems and methods for wireless communication of long data units

---

US20140003415A1|2014-01-02|Systems and methods for enhanced wireless communication frames

---

JP5989831B2|2016-09-07|System, method and device for performing interleaving

---

US20130179755A1|2013-07-11|Systems and methods for low density parity check tone mapping

同族专利:

---

公开号 | 公开日

---

KR20150100952A|2015-09-02|

---

US9049155B2|2015-06-02|

---

JP6312738B2|2018-04-18|

---

JP2014531805A|2014-11-27|

---

KR101590893B1|2016-02-02|

---

HUE037566T2|2018-09-28|

---

MX336542B|2016-01-22|

---

CN103918235A|2014-07-09|

---

US20140369263A1|2014-12-18|

---

CN104253672A|2014-12-31|

---

CN104243100A|2014-12-24|

---

HK1203708A1|2015-10-30|

---

EP3116157B1|2018-04-18|

---

JP5937215B2|2016-06-22|

---

RU2014113423A|2015-10-20|

---

KR20140072087A|2014-06-12|

---

ES2676519T3|2018-07-20|

---

HK1197327A1|2015-01-09|

---

CA2845596A1|2013-03-14|

---

KR101883920B1|2018-08-01|

---

ES2675748T3|2018-07-12|

---

WO2013036642A1|2013-03-14|

---

KR20150100951A|2015-09-02|

---

CN104253672B|2017-12-19|

---

HK1203707A1|2015-10-30|

---

JP2016187183A|2016-10-27|

---

MX2014002611A|2014-04-14|

---

US20130235860A1|2013-09-12|

---

EP2754276A1|2014-07-16|

---

CN103918235B|2017-08-04|

---

CA2942955A1|2013-03-14|

---

EP3113434A3|2017-03-08|

---

EP2754276B1|2018-04-04|

---

EP3116157A1|2017-01-11|

---

US9210611B2|2015-12-08|

---

US9071990B2|2015-06-30|

---

HUE039166T2|2018-12-28|

---

JP2016187184A|2016-10-27|

---

US20150023288A1|2015-01-22|

---

CN104243100B|2018-06-19|

---

KR101855443B1|2018-05-08|

---

EP3113434A2|2017-01-04|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US6804237B1|1999-06-23|2004-10-12|Nortel Networks Limited|Method, devices and signals for multiplexing payload data for transport in a data network|

---

US6633564B1|1999-09-22|2003-10-14|Nortel Networks Limited|Method and apparatus for inserting packets into a data stream|

---

US20010033554A1|2000-02-18|2001-10-25|Arun Ayyagari|Proxy-bridge connecting remote users to a limited connectivity network|

---

CN1386390A|2000-05-22|2002-12-18|索尼公司|Data transmission method, and transmission system, and data transmission device|

---

US7224693B1|2000-08-11|2007-05-29|Ericsson Ab|Long packet handling|

---

CN1830171B|2003-06-27|2010-05-05|诺基亚公司|Method and apparatus for packet aggregation in a wireless communication network|

---

JP4005974B2|2004-01-09|2007-11-14|株式会社東芝|COMMUNICATION DEVICE, COMMUNICATION METHOD, AND COMMUNICATION SYSTEM|

---

JP4086304B2|2004-04-23|2008-05-14|株式会社東芝|Communication apparatus, communication system, and communication control program|

---

US7876848B2|2004-07-27|2011-01-25|Samsung Electronics Co., Ltd.|Apparatus and method for transmitting a data stream in a wireless communication system with multiple antennas|

---

KR100691288B1|2005-12-01|2007-03-12|한국전자통신연구원|A method of proactive coordinator appropriation for piconet device|

---

US7620880B2|2005-12-20|2009-11-17|Samsung Electronics Co., Ltd.|LDPC concatenation rules for IEEE 802.11n system with packets length specified in OFDM symbols|

---

EP1808994A1|2006-01-12|2007-07-18|Alcatel Lucent|Universal switch for transporting packet data frames|

---

JP4697068B2|2006-06-27|2011-06-08|ソニー株式会社|Wireless communication system, wireless communication apparatus, wireless communication method, and computer program|

---

US8787841B2|2006-06-27|2014-07-22|Qualcomm Incorporated|Method and system for providing beamforming feedback in wireless communication systems|

---

JP4257347B2|2006-07-11|2009-04-22|株式会社東芝|Communication device, display terminal, and communication program|

---

US8706048B2|2006-07-14|2014-04-22|Broadcom Corporation|Method and system for explicit feedback with sounding packet for wireless local area networks |

---

EP2119291B1|2006-12-29|2016-08-24|Telefonaktiebolaget LM Ericsson |Automatic distribution of server and gateway information for pool configuration|

---

US8351368B2|2007-10-05|2013-01-08|Entropic Communications, Inc.|Method for extended rate/range communication over a communication network|

---

US8630309B2|2008-09-10|2014-01-14|Electronics And Telecommunications Research Institute|Frame generation apparatus and method of protecting protocol header information over wideband high frequency wireless system|

---

CN101741710B|2008-11-04|2011-12-07|电信科学技术研究院|Uplink-downlink configuration and receiving methods of TDD system carrier aggregation|

---

EP2375853A4|2009-01-06|2013-11-20|Alcatel Lucent|A base station, relay station, mobile terminal for relaying and the method thereof|

---

JPWO2010089825A1|2009-02-04|2012-08-09|パナソニック株式会社|Radio communication base station apparatus, radio communication terminal apparatus, and radio communication method|

---

CN102396186B|2009-04-13|2014-12-10|马维尔国际贸易有限公司|Physical layer frame format for wlan|

---

US8755363B2|2009-09-15|2014-06-17|Qualcomm Incorporated|Physical layer signaling of control parameters|

---

US8630274B2|2009-10-28|2014-01-14|Electronics And Telecommunications Research Institute|Method for protecting opportunity to transmit data frame in wireless LAN system|

---

US8873461B2|2010-02-12|2014-10-28|Electronics And Telecommunications Research Institute|Packet transmission/reception method and apparatus in wireless communication system|

---

KR101800171B1|2010-03-12|2017-11-24|한국전자통신연구원|Method and apparatus for transmitting/receiving packet in wireless communication system|

---

US8855067B2|2010-04-02|2014-10-07|Marvell World Trade Ltd.|Multi-user communication group management and signaling|

---

US8155102B1|2011-05-24|2012-04-10|Renesas Mobile Corporation|Channel access control|

---

US9100275B2|2011-09-06|2015-08-04|Sameer Vermani|Signal unit including a field indicative of a zero-length payload|

---

US9049155B2|2011-09-06|2015-06-02|Qualcomm Incorporated|Dual interpretation of a length field of a signal unit|US9094175B2|2010-07-16|2015-07-28|Qualcomm, Incorporated|Method and apparatus for saving power by using signal field of preamble|

---

US20130315323A1|2011-04-24|2013-11-28|Broadcom Corporation|Traveling pilots within single user, multiple user, multiple access, and/or MIMO wireless communications|

---

US9100275B2|2011-09-06|2015-08-04|Sameer Vermani|Signal unit including a field indicative of a zero-length payload|

---

US9049155B2|2011-09-06|2015-06-02|Qualcomm Incorporated|Dual interpretation of a length field of a signal unit|

---

CN108449299B|2011-10-07|2022-01-14|英特尔公司|Method and arrangement for communication in a low power wireless network|

---

CN103095425A|2011-10-31|2013-05-08|华为技术有限公司|Method and device transmitting acknowledgement frame in wireless local area network|

---

US9071489B2|2011-12-07|2015-06-30|Futurewei Technologies, Inc.|System and method for preambles in a wireless communications network|

---

US9300510B2|2011-12-08|2016-03-29|Lg Electronics Inc.|Method of transmitting and receiving data unit in wireless local area network system and apparatus for the same|

---

WO2013104992A2|2012-01-11|2013-07-18|Marvell World Trade Ltd.|Information bit padding schemes for wlan|

---

WO2013123395A1|2012-02-15|2013-08-22|Marvell Word Trade Ltd.|Low bandwidth phy transmission in a wider bandwidth|

---

US8750215B2|2012-03-06|2014-06-10|Intel Corporation|Method and apparatus for a 1 MHz long training field design|

---

US9319896B2|2012-05-03|2016-04-19|MEDIATEK Singapore Ple. Ltd.|Beam-change indication for channel estimation improvement in wireless networks|

---

US9559810B2|2012-09-10|2017-01-31|Intel Corporation|Methods and arrangements for a check sequence|

---

US9467898B2|2012-09-28|2016-10-11|Futurewei Technologies, Inc.|System and method for response frame type indication|

---

MX346536B|2013-02-15|2017-03-24|Lg Electronics Inc|Method and device for transmitting/receiving frame in accordance with bandwidth thereof in wlan system.|

---

KR20160003743A|2013-05-03|2016-01-11|마벨 월드 트레이드 리미티드|Beam change and smoothing recommendation in mixed mode wlan systems|

---

US9398579B2|2013-05-03|2016-07-19|Qualcomm Incorporated|Systems and methods for downlink frequency domain multiplexing transmissions|

---

EP2991283A4|2013-06-27|2016-07-27|Huawei Tech Co Ltd|Data transmission method and apparatus|

---

EP2993848B1|2013-06-27|2019-04-03|Huawei Technologies Co., Ltd.|Data transmission method and apparatus|

---

US20150117558A1|2013-10-25|2015-04-30|Samsung Electronics Co., Ltd.|Orthogonal frequency-division multiplexingpeak to average power ratioreduction using low complexity transformations|

---

CN104683058B|2013-11-28|2019-11-29|中兴通讯股份有限公司|Wireless frame sending method, device and base station|

---

US9876614B1|2014-01-20|2018-01-23|Marvell International Ltd.|Hybrid automatic repeat request for wireless local area network|

---

US10652936B2|2014-03-21|2020-05-12|Nokia Technologies Oy|Short identifiers for device-to-devicebroadcast communications|

---

EP3131249B1|2014-04-09|2019-03-06|LG Electronics Inc.|Method for transmitting mixed ppdu in he-wlan and device using same|

---

US10225124B2|2014-07-28|2019-03-05|Lg Electronics Inc.|Transmitting and receiving device and method in wireless communication system|

---

EP3591883B1|2014-09-12|2021-03-10|Newracom, Inc.|System and method for packet information indication in communication systems|

---

US20160204915A1|2015-01-14|2016-07-14|Xiaogang Chen|Apparatus, computer readable medium, and method for generating and receiving signal fields in a high efficiency wireless local-area network|

---

KR102061123B1|2015-02-02|2019-12-31|후아웨이 테크놀러지 컴퍼니 리미티드|Resource indication method and device|

---

US20160286011A1|2015-03-26|2016-09-29|Assaf Kasher|Techniques for communicating an end of packet indicator|

---

KR102107094B1|2018-12-06|2020-05-06|한국생산기술연구원|Discharge tube manufactured using laser and manufacturing method thereof|

---

CN110535805B|2019-09-26|2020-12-04|中山大学|Additional information transmission method based on constellation rotation|

法律状态:
2020-11-03| B08F| Application dismissed because of non-payment of annual fees [chapter 8.6 patent gazette]|Free format text: REFERENTE A 8A ANUIDADE. |

---

2021-02-23| B08K| Patent lapsed as no evidence of payment of the annual fee has been furnished to inpi [chapter 8.11 patent gazette]|Free format text: EM VIRTUDE DO ARQUIVAMENTO PUBLICADO NA RPI 2600 DE 03-11-2020 E CONSIDERANDO AUSENCIA DE MANIFESTACAO DENTRO DOS PRAZOS LEGAIS, INFORMO QUE CABE SER MANTIDO O ARQUIVAMENTO DO PEDIDO DE PATENTE, CONFORME O DISPOSTO NO ARTIGO 12, DA RESOLUCAO 113/2013. |

---

2021-09-21| B350| Update of information on the portal [chapter 15.35 patent gazette]|

---

2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201161531584P| true| 2011-09-06|2011-09-06|

---

US61/531,584|2011-09-06|

---

US201161562063P| true| 2011-11-21|2011-11-21|

---

US61/562,063|2011-11-21|

---

US201161564177P| true| 2011-11-28|2011-11-28|

---

US61/564,177|2011-11-28|

---

US201161566961P| true| 2011-12-05|2011-12-05|

---

US61/566,961|2011-12-05|

---

US201161580616P| true| 2011-12-27|2011-12-27|

---

US61/580,616|2011-12-27|

---

US201261585479P| true| 2012-01-11|2012-01-11|

---

US201261585573P| true| 2012-01-11|2012-01-11|

---

US61/585,479|2012-01-11|

---

US61/585,573|2012-01-11|

---

US201261670092P| true| 2012-07-10|2012-07-10|

---

US61/670,092|2012-07-10|

---

US201261684248P| true| 2012-08-17|2012-08-17|

---

US61/684,248|2012-08-17|

---

US13/604,030|2012-09-05|

---

US13/604,030|US9049155B2|2011-09-06|2012-09-05|Dual interpretation of a length field of a signal unit|

---

PCT/US2012/053966|WO2013036642A1|2011-09-06|2012-09-06|Dual interpretation of a length field of a signal unit|

---